GitHub Team plans can now configure and enforce organization-level rulesets! Previously, this powerful governance capability was limited to Enterprise plans, but now Team plan customers can scale their use of branch and tag protections across multiple repositories with ease.

Screenshot of a ruleset page targeting multipule repositories.

🆕 What’s new

  • Organization rulesets can now be targeted and enforced at the organization level for Team plan customers.
  • Administrators can define, simplifying configuration and ensuring consistent enforcement of branch and tag protections.
  • This unlocks advanced compliance and management features for more organizations, helping teams govern how code enters their repositories at scale.

🧰 Benefits

  • Governance at scale: Apply consistent rules for branch and tag protections across all or select repositories in your organization.
  • Streamlined compliance: Enforce requirements such as requiring pull requests, requiring GitHub Actions workflows, and more organization-wide. This reduces manual configuration and the risk of drift.
  • Accelerate Copilot code review rollout: Using organization rulesets, you can seamlessly enable Copilot code review for all repositories, ensuring uniform adoption.

🔗 Getting started

Using the ruleset-recipes, repository you can quickly import pre-made rulesets to quickly get started. Organization-level rulesets can be managed via the UI, REST API, or GraphQL API. For more details, refer to our documentation on managing rulesets.

Join the discussion within the GitHub Community.