What is the purpose of GitHub's 'Required workflows' feature at the organization level?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Required workflows at the org level are centralized quality gates. Define a security scan workflow once in a designated repository, mark it as required, and it runs on every PR across every repo in the org — without each repo needing to define it.
Full explanation below image
Full Explanation
GitHub's Required Workflows feature (available on Enterprise plans) allows organization owners to define workflows that automatically run on pull requests across multiple repositories, even if those repositories don't have the workflow file in their own codebase. How it works: (1) A workflow is defined in a source repository within the organization. (2) Organization owners mark it as a required workflow and specify target repositories (all repos or selected). (3) The workflow runs automatically on PRs in target repositories. (4) The PR cannot be merged until the required workflow passes. Use cases: mandatory security scanning across all repos, compliance checks, code quality gates enforced at the org level without per-repo configuration. This ensures consistent security and quality standards without relying on individual teams to implement them.