Bulk migrate branch protections to rulesets for a repository

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd"> You can now convert all branch protection rules of a repository to rulesets in a single action. This is an extension of the ability to convert a single branch protection rule to a ruleset that we released previously, now allowing for at-scale conversions.

How it works

Navigate to Settings → Rulesets in your repository and click Import branch protection rules. In the Review import dialog, you can:

Preview the rulesets that will be created before you confirm the conversion.

See which branch protection rules are already covered by an existing ruleset.

Review cases where one branch protection rule produces multiple rulesets to preserve its original behavior.

Choose an enforcement status (e.g., Active, Evaluate, or Disabled) and select which rulesets to create.

After you click Create rulesets, choose whether to keep or delete the original branch protection rules.

Why migrate to rulesets?

Rulesets offer several advantages over classic branch protections:

Apply rules across multiple branches with pattern matching

Layer multiple rulesets for granular policy control

Manage rulesets at the organization or enterprise level

Configure fine-grained bypass permissions for users, teams, and apps

Availability

This feature is available for all repositories where rulesets are available. Learn more about converting your branch protections to repository rulesets.

Join the discussion within GitHub Community.

The post Bulk migrate branch protections to rulesets for a repository appeared first on The GitHub Blog.