GitHub now lets maintainers import all of a repository’s classic branch-protection rules into rulesets in one action. The review dialog previews the proposed rules, flags existing coverage, and lets the owner select Active, Evaluate, or Disabled enforcement before applying changes.
Rulesets are useful when the same policies should cover multiple branches or when agents need carefully scoped bypass permissions. For a small project, this may simplify an accumulation of hand-configured branch restrictions; for a simple repository it may be unnecessary complexity.
GitHub leaves the choice to keep or delete the original rules after conversion. Treat the migration as a configuration change, not a cosmetic reorganization, and inspect the resulting enforcement before removing older protections.
What to do: On a noncritical repository, review Settings → Rulesets → Import branch protection rules; preview first and leave existing protections intact until tested.