GitHub adds bulk migration from branch protections to repository rulesets

GitHub has introduced a bulk conversion feature that lets repository administrators turn every classic branch‑protection rule into a repository ruleset with a single action.

To start, users go to Settings → Rulesets in the repository and click the Import branch protection rules button. The Review import dialog then shows a preview of the rulesets that will be generated, highlights any existing rulesets that already cover a rule, and flags cases where one branch‑protection rule would be split into multiple rulesets to keep its behavior intact. Administrators can pick an enforcement status such as Active, Evaluate, or Disabled for each new ruleset and decide which of the proposed rulesets to create.

When the Create rulesets button is pressed, the interface offers the choice to retain the original branch‑protection rules or delete them after the migration completes.

GitHub promotes rulesets because they allow policies to be applied across many branches using pattern matching, enable layered rulesets for finer‑grained control, and can be managed at the organization or enterprise level. They also support fine‑grained bypass permissions for specific users, teams, and applications. Unlike classic branch protections, multiple rulesets may apply to the same branch simultaneously, and users with read access can view the active rulesets, giving clearer visibility and control.

The bulk migration is available for any repository where rulesets are supported, which includes public repositories on GitHub Free and private repositories on GitHub Pro, Team, and Enterprise Cloud plans. Only people with admin access or a custom role that includes the “edit repository rules” permission can create, edit, or delete rulesets. GitHub advises administrators to review the proposed rulesets before finalizing the conversion to ensure the new configuration behaves as expected.