required-status-checks

Required status checks gate pull request merges by enforcing CI tests, security scans, and linting to pass. You enable the workflow in your repository and configure branch protection to require these defined CI checks before allowing any merges.

Yes, you can require security scans and linting to pass before merging a pull request. The workflow integrates linting and security scanning actions into your CI pipeline, ensuring these checks are configured as required contexts in your branch protection rules.

To configure branch protection to require CI checks, enable the workflow in your repository and update your branch protection rules to require the defined CI contexts. This setup supports configurable contexts and strict mode for different teams.

Branch protection enforcement supports strict mode and reusable workflows for different teams. It provides configurable contexts to gate merges, along with examples and reference docs to guide implementation and auditing of your CI checks.

Untested or insecure code merges bypass pipelines when branch protections lack required status checks. Enforcing CI gates ensures that tests, security scans, and linting pass before code is merged, improving repository quality and compliance.