ci-validate-workflow

Validate GitHub Actions workflows using YAML syntax checking and GitHub Actions-specific linting tools to catch syntax errors, invalid action versions, and missing required fields before pushing code. This prevents broken CI/CD pipelines and saves debugging time.

Best practices for GitHub Actions workflows include pinning action versions to specific SHAs instead of floating tags, setting timeouts for steps, ensuring runs-on is specified, verifying secrets and variables are available, and confirming all steps reference valid actions.

Yes, you can check GitHub Actions workflows locally using actionlint and yamllint to detect common issues such as syntax errors, incorrect context usage, missing fields, and invalid action references before CI runs.

Validating workflow YAML locally catches configuration errors early, preventing failed CI/CD runs and accelerating development cycles. Early detection saves time compared to discovering errors when GitHub Actions executes the workflow.

Yes, actionlint specializes in validating GitHub Actions workflows for syntax, best practices, and correctness. It checks action versions, step definitions, trigger configurations, and context usage specific to GitHub Actions.

Validate GitHub Actions workflows using gh (GitHub CLI), actionlint for GitHub Actions-specific rules, and yamllint for YAML syntax. These tools together ensure syntax correctness, best practice compliance, and proper workflow structure.