preflight

Branch-scoped linting targets only modified files by comparing your branch against its base. This change-gated preflight identifies relevant updates and runs ESLint, markdownlint, and actionlint exclusively on them to ensure code quality before merging.

The preflight process classifies linting violations as either introduced or pre-existing. By evaluating branch changes against the base, it separates new errors from legacy issues and handles them accordingly to keep your CI/CD pipeline focused on current changes.

Yes, you can integrate this linting preflight directly into a CI/CD workflow as a quality gate. It automates the linting process for code changes in a branch, ensuring that introduced violations are caught and resolved before merging.

Yes, branch-scoped linting requires ESLint, markdownlint-cli2, and actionlint installed in your environment. These dependencies execute the actual code, markdown, and GitHub Actions validation checks against the files changed in your branch.

Automating pre-commit linting for GitHub Actions and Markdown is best handled by a change-gated preflight script. It automatically detects branch changes and runs actionlint and markdownlint only on modified files to reduce manual work and improve CI/CD efficiency.

Change-gated linting reduces unnecessary linter execution by only checking files a branch has changed compared to its base. This reduces manual work, speeds up CI/CD pipelines, and isolates introduced violations from pre-existing errors in the codebase.