Skip to content

Rulesets overview

A ruleset is GitHub’s rule object. It targets branches or tags, applies rules to them, and can name who may bypass those rules. Bundu uses rulesets for branch and tag protection. Classic branch protection is not used on the default branch.

Level Set on What it holds
Enterprise the bundu-labs enterprise The floor for every organization: pull requests, no force-push, no deletion, tag protection, and central workflows that run on every pull request.
Organization the bundu-labs organization The required status checks and the required workflows that gate a merge to main.
Repository each repository Only what is specific to that repository. bundu-docs adds a merge queue.

GitHub applies every ruleset that matches a branch, and the rules add up. A ruleset lower down cannot remove a rule set above it. Bypass is the only way around a rule, and bypass is granted per ruleset.

  • A new repository is covered on creation. Nothing has to be configured in it for the floor, the lint gate and the release gates to apply.
  • One change applies everywhere. A rule changed at the enterprise or organization level takes effect in every repository it covers. No repository can drift from the standard by accident.
  • Repositories carry only their own differences. A repository ruleset holds what is specific to it, such as its merge queue, and never repeats a rule from above.

Each ruleset is in one of three modes:

  • active: rules block the action they cover.
  • evaluate: rules are checked and the results are shown, but nothing is blocked.
  • disabled: the ruleset does nothing.

Three enterprise rulesets are in evaluate today: code scanning, repository standards and Semgrep. Their results are reported but do not block a merge at the enterprise level. The organization and repository rules, and the other enterprise rulesets, are active.

As read from the GitHub API. “Default branch” means main for bundu-docs.

Ruleset Level Targets Mode What it does
enterprise-main-protection Enterprise Default branch, all organizations active Pull request required, 0 approvals; no force-push; no deletion.
enterprise-release-version-check Enterprise Default branch active Requires the release version check workflow.
enterprise-dependency-review Enterprise Default branch active Requires the dependency review workflow.
enterprise-org-workflows Enterprise Default branch active Requires the PR metadata and repository standards workflows.
enterprise-release-tag-protection Enterprise Tags v[0-9]*.[0-9]*.[0-9]* active No deletion, no force-update, no non-fast-forward.
enterprise-staging-protection Enterprise Branch staging active Restricts creating a staging branch. No other rule.
enterprise-code-scanning Enterprise Default branch evaluate Requires CodeQL, reporting high-severity alerts.
enterprise-semgrep Enterprise Default branch evaluate Requires the Semgrep workflow.
enterprise-repo-standards Enterprise Default branch evaluate Requires the repository standards workflow.
org-wide-main-protection Organization Default branch, all repositories active Seven required status checks; pull request; no force-push; no deletion; two required workflows.
merge-queue-main Repository Default branch of bundu-docs active Merge queue, merge method MERGE.

The detail for each level is on its own page: enterprise, organization and repository.

Where the live configuration differs from the written standard

Section titled “Where the live configuration differs from the written standard”

The written standard is in ORG_SETTINGS.md and settings/README.md in nyuchi/.github, and in the bundu-labs README and AGENTS.md. Checked against the API, these differences exist today:

  • Linear history is not required on main. The bundu-labs README says the enterprise ruleset requires it. The live enterprise and organization rulesets do not. No live ruleset requires linear history: enterprise-staging-protection did until its linear-history rule was removed on 2026-11-21.
  • Branches are not required to be up to date. The organization ruleset has strict_required_status_checks_policy set to false. The written standard says the setting is enabled. The merge queue tests each entry against the latest main in any case.
  • The organization ruleset requires seven status checks, not five. The written standard lists five lint checks. The seven are lint / actionlint, lint / markdownlint, lint / yamllint, vite-plus / fmt, vite-plus / check, vite-plus / test and vite-plus / build.
  • Two sources for central workflows. The enterprise rulesets name workflows in nyuchi/.github. The organization ruleset names workflows in bundu-labs/.github. The source is described as moving to bundu-labs/.github; until that happens, both are in use.
  • The enterprise rulesets no longer target staging, except to block it. As of 2026-11-21, the six enterprise rulesets listed above (enterprise-release-version-check, enterprise-dependency-review, enterprise-org-workflows, enterprise-code-scanning, enterprise-semgrep and enterprise-repo-standards) target only the default branch. enterprise-staging-protection has only a creation rule on staging. Enterprise owners and the bundu-release GitHub App can still create a staging branch. There is no staging branch in this repository. Some central release tooling and written standards may still refer to staging; this update did not check them.