doctor

To check repository readiness for the kampus-pipeline, run a pre-flight verification that scans for required labels, GitHub CLI authentication, and CI workflows. This provides a tiered checklist with detailed fix commands to resolve any missing prerequisites.

A CI workflow verification checklist includes validating required GitHub labels, confirming authentication setup, and ensuring CI workflows are present. It uses a tiered system to prioritize critical pipeline checks and offers detailed fix commands for any gaps found.

Yes, you need GitHub CLI and npm installed to verify repository prerequisites. GitHub CLI handles label management and authentication checks, while npm resolves package dependencies required for the verification scripts to run successfully.

Yes, you can run a pipeline readiness check on any repository regardless of its current setup. The verification is repo-agnostic, meaning it operates on any codebase looking to adopt the kampus-pipeline and identifies missing labels or workflows.

Your kampus-pipeline run may fail during the CI workflow stage if the repository lacks required labels, proper authentication, or configured CI workflows. Running a pre-flight checklist identifies these specific gaps and provides fix commands to ensure a smooth pipeline run.

The best way to prepare a repository for a new CI pipeline is to run an automated pre-flight check that verifies required labels, authentication, and CI workflows. This ensures a smooth, error-free pipeline run by providing a tiered checklist of critical repository configurations.