Generates GitHub Ruleset JSON for the three v4 branches. After downloading, import each in your consumer repo: Settings → Rules → Rulesets → New ruleset → "Import a ruleset".
Bot bypass is pre-added by default. With the checkbox above left on, the generated next.json / hotfixes.json already list your bot App in bypass_actors — no manual step needed. The v4 reset/merge workflows (§6.3, §7.2) push as the bot and would otherwise be blocked by non_fast_forward / require-PR.
If you opted out (or left the App ID blank), add it after import: open the imported ruleset → Bypass list → Add bypass → select your bot's GitHub App. master never needs bot bypass.
master.json — production branch
next.json — integration branch
hotfixes.json — hotfixes lane
Notes:
The required-check name is hardcoded as ✅ Required PR Check. If your repo's check uses a different name, edit the imported ruleset after import.
Merge methods are per-branch: master uses ["squash"] so each release lands as one clean commit; next and hotfixes use ["merge"] only — "Create a merge commit" preserves the PR's original signed commits intact. GitHub's "Rebase and merge" web-UI button re-creates commits server-side and strips GPG signatures, so it's deliberately disallowed on the staging branches. The slightly noisier git log on next/hotfixes is invisible at the master level: the master squash collapses the entire range (merge commits included) into one clean signed commit per release.
next.json intentionally omits required_linear_history so §7.2's master-into-next API merge can produce a merge commit when needed.
The bot App is pre-added to next/hotfixesbypass_actors by default (uncheck the box, or blank the App ID, to opt out). It is never added to master.