Gutenberg Repository Migrates Branch Protection Rules to Rulesets
Migrate Gutenberg branch protection rules to rulesets to fix the plugin release process and ensure consistent enforcement.
Check that all Gutenberg repo rulesets enforce the same restrictions as before and report any discrepancies.
Summary
Gutenberg has converted all branch protection rules to the newer repository rulesets, a change that fixes a broken step in the plugin release process where the GitHub app could not push version‑bump commits to trunk. Rulesets offer more flexibility, allow layering, and are publicly visible to contributors, unlike the legacy protection rules. The migration was performed to ensure the new rulesets function identically to the previous protection rules, though some nuances may have been missed. The change removes the need to maintain separate branch protection rules and aligns Gutenberg with GitHub’s latest best practices. Developers should verify that the new rulesets enforce the same restrictions on pull requests, status checks, and required reviewers as before. Any permission or capability issues should be reported in the core‑editor Slack channel for quick resolution.
Key changes
- All branch protection rules replaced by repository rulesets.
- Rulesets provide more flexibility and can be layered.
- Rulesets are publicly accessible to contributors.
- Migration fixes GitHub app inability to push version‑bump commits to trunk.
- No benefit found in keeping old branch protection rules.
- Developers must verify that new rulesets match previous restrictions.