validation-tools

To lint Dockerfiles and shell scripts before pushing, run hadolint on Dockerfiles and shellcheck on shell scripts. This local validation catches syntax errors and best-practice issues early in development workflows to prevent broken deployments.

Validating GitHub workflow YAML files locally is best done using actionlint on .github/workflows/*.yml files and yamllint for general YAML syntax. This catches workflow configuration errors before merging changes to ensure reliable CI/CD pipelines.

Yes, you can use yq to query and parse YAML files during CI/CD validation. It complements linters like yamllint by allowing you to extract and verify specific configuration values within your YAML workflows before deployment.

Local CI/CD validation reduces faulty deployments by catching syntax errors and best-practice issues in Dockerfiles, shell scripts, and YAML workflows before code is pushed. Running hadolint, shellcheck, and actionlint locally ensures configurations are reliable.

Yes, this validation approach provides local guidance and usage examples for hadolint, shellcheck, actionlint, yamllint, and yq without requiring external dependencies. It integrates directly into development workflows and code review processes.

You need to run actionlint during your development workflow before merging changes to GitHub workflows. Applying actionlint to .github/workflows/*.yml files catches syntax errors and best-practice issues in CI/CD configurations early.