my-git

Rulesets

English

中文

GitHub Rulesets are used to uniformly control branch, tag, and push behaviors.

They are more suited for organizational and repository-level unified governance than single branch protection rules.

Suitable Scenarios

Multiple branches require unified rules
Multiple repositories within an organization require unified standards
Requires enabling, pausing, and auditing of rules
Needs to restrict specific paths, file sizes, or commit metadata
Desires centralized management of branch rules and tag rules

What Can Be Controlled

Common rules include:

Restrict branch creation, updates, and deletion
Require PRs for merging
Require status checks to pass
Require linear history
Restrict force pushes
Protect tags
Set rules for specific paths

Different rule capabilities vary depending on the GitHub version and repository type; rely on the official documentation and settings page for actual details.

Relationship with Branch Protection

Rulesets and Branch Protection can coexist.

The official GitHub documentation states that when multiple rulesets hit the same target, the rules will be aggregated.

New teams should start with Branch Protection first. Once there are many repositories and complex rules, gradually switch to Rulesets.

Recommended Implementation Sequence

Protect main first
Then protect release/*
Then abstract into a ruleset
Then roll out to multiple repositories within the organization
Periodically audit whether rules are still valid

Recommendations for Multi-Repository Teams

In scenarios like 40+ microservices, the value of Rulesets lies in unifying baselines:

Default branches must go through PRs
Required check names must remain consistent
Prohibit regular members from deleting or force pushing critical branches
Release branches and tags have separate rules
High-risk repositories retain stricter configurations

Rulesets are suited for expressing unified rules, while specific differences within a repository still need clear explanations preserved.

Compared to traditional Branch Protection, Rulesets are more suited for multi-rule stacking, organizational baselines, and multi-repository governance. New teams can start with Branch Protection and migrate to Rulesets as the number of repositories grows.