القائمة
Master branch protection rules, bypass policy, and how to modify when needed
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
How to bump package versions in kuskus — required before merging any PR that touches a package
How to update SHA-pinned GitHub Actions in kuskus workflows
Opening and reviewing PRs in the kuskus repo
Triage and label issues in the kuskus repo
How automated publishing works in kuskus
Rules for safe development on this live, published extension
| name | Kuskus-Branch-Protection |
| description | Master branch protection rules, bypass policy, and how to modify when needed |
Master is protected by a GitHub Ruleset (not classic branch protection). All changes must go through a PR. No external approval required — the maintainer (rosshamish) reviews and merges their own PRs.
Ruleset: "Protect master" (ID: 13087704)
URL: https://github.com/rosshamish/kuskus/rules/13087704
bypass_mode: always) — this covers:
TOKEN_GITHUB (your admin PAT) — version bump pushes workGITHUB_TOKEN (write-level, not admin) pushing to master directly# View current ruleset configuration
gh api repos/rosshamish/kuskus/rulesets/13087704 | python3 -m json.tool
# List all rulesets
gh api repos/rosshamish/kuskus/rulesets | python3 -m json.tool
Or via the UI: https://github.com/rosshamish/kuskus/rules/13087704
Ruleset deletion, enforcement changes, and protection bypass are documented in a private runbook. Contact the maintainer.
Classic branch protection doesn't support bypass actors on personal (non-org) repos. Rulesets work everywhere and are more flexible.
The publish workflows use GITHUB_TOKEN: ${{ secrets.TOKEN_GITHUB }} (rosshamish's admin PAT) for the version bump commit. Since admin bypasses the ruleset, version bump pushes to master continue to work without change.
If TOKEN_GITHUB is ever rotated/revoked, re-add the new PAT as the secret in repo settings, or switch to a deploy key with admin access.