github
GitHub Actions Required workflows - GA
Summary
The importance of enforcing a set of quality standards to continuously deploy in a consistent and predictable way can’t be underestimated. Implementing these standards without the duplication of CI/CD configuration code is a challenge many organizations face today. How can workflows solve these problems and allow the ability to “push things down” or enforce requirements from organization down to its repositories?
We are building the controls that allow an organization to require a workflow file (or list of workflow files) to pass before code is merged into any of its repositories. Requiring a workflow to pass before merging will be available via Rulesets and will allow access to controls already available to branch rulesets, such as:
- enforcement status
- bypass rules
- repository targeting
By requiring a workflow to pass before merging will allow organization admins to specify:
- which workflow file to run from any of the organization’s repositories
- a specific branch or tag for the workflow file
- an exact commit sha to pin to the required workflow (optional)
Required workflows can help companies with the following use cases:
- Correctness and Compliance: Ensure that all code meets an enterprise’s quality standards before merging.
- DRY: Reducing duplication of CI/CD configuration code
🚢 This has shipped: https://github.blog/changelog/2023-10-11-requiring-workflows-with-repository-rules-is-generally-available/
Leaving open to track for GHES release!
🚢 This has shipped with GHES 3.12: https://docs.github.com/en/[email protected]/admin/release-notes
Closing as complete!