Requiring Actions workflows with Repository Rules is now generally available on GitHub.com!
Through Repository Rules, GitHub Enterprise Cloud customers can now set up organization-wide rules to enforce their CI/CD workflows, ensuring workflows pass before pull requests can be merged into target repositories. Additional settings allow for fine-tuning how the workflow file can be selected — either from a specific branch, tag, or SHA — and provide maximum control over the version expected to run.
Applying a newly created workflow policy across an organization can feel risky. To ensure confidence when enabling a workflow rule across targeted repositories, workflow rules can be put into “evaluate” mode which will validate the rule is working correctly. And don’t worry, organization administrators can even allow select roles to “break the glass” and bypass a rule when necessary.
Learn more about this release and how requiring workflows with Repository Rules can protect your repositories.
To share feedback or ask questions, join our Community Discussion!
The post Requiring workflows with Repository Rules is generally available appeared first on The GitHub Blog.