Enterprise rulesets
The enterprise rulesets are set once, on the bundu-labs enterprise. Their conditions cover every organization in the enterprise. Most of them exclude repositories whose names begin with sandbox- or archive-; the tag and staging rulesets do not. They hold the floor that no organization can lower.
Each ruleset below is listed with its target, its mode and its bypass actors, followed by the reason for it. Bypass actors are described by role. The bundu-release GitHub App is the only app named in any bypass list in the enterprise or organization rulesets.
The floor: enterprise-main-protection
Section titled “The floor: enterprise-main-protection”- Target: the default branch of every repository.
- Mode:
active. - Rules: a pull request is required with 0 approving reviews; review threads must be resolved; force-pushes are blocked; deletion is blocked. Allowed merge methods are merge, squash and rebase. There are no status checks at this level.
- Bypass: enterprise owners, always. Organization admins, for the pull request requirement only.
Why. Every change to main is a pull request, so there is a record of it and the central checks run on it. Force-push and deletion are blocked so that history cannot be rewritten underneath a release. The approval count is 0 because the Nyuchi standard that Bundu follows sets it to 0 during the solo-developer phase, and says to raise it to 1 once a second engineer has merge rights. Linear history is not required here (see the overview of differences).
Central workflows that run on every pull request
Section titled “Central workflows that run on every pull request”These rulesets make a central workflow a required check for each pull request into the default branch. The workflows are read from nyuchi/.github, pinned to its main branch. A workflow run this way ignores its own on: filters, so it decides for itself which events it handles.
| Ruleset | Targets | Mode | Required workflow (nyuchi/.github) |
Why |
|---|---|---|---|---|
enterprise-release-version-check |
Default branch | active | release-version-check.yml |
Refuses a pull request that writes a version the versioning policy does not allow next. See releases. |
enterprise-dependency-review |
Default branch | active | dependency-review.yml |
Fails a pull request that adds a package with a known high-severity advisory. |
enterprise-org-workflows |
Default branch | active | pr-metadata.yml and repo-standards.yml |
Adds the assignee, labels and description, and checks repository standards. |
enterprise-repo-standards |
Default branch | evaluate | repo-standards.yml |
Fails a pull request that adds CLAUDE.md or .claude/ to an org .github repository. Currently report-only. |
enterprise-semgrep |
Default branch | evaluate | reusable-semgrep.yml |
Static analysis of changed files with the open-source Semgrep CLI. Currently report-only. |
enterprise-code-scanning |
Default branch | evaluate | CodeQL, alerts at high_or_higher severity |
Code scanning on the default branch. Currently report-only. |
Note: enterprise-org-workflows and enterprise-repo-standards both require repo-standards.yml. The overlap is not harmful, but the second ruleset is the one still in evaluate.
Why the version check is enterprise-wide. A version written into a file such as package.json must follow the same policy in every repository, and the policy is one script. Putting the check at the enterprise level means no repository can skip it by changing its own settings.
Why dependency review is enterprise-wide. A new dependency with a known high-severity advisory is the most common way a vulnerable package reaches production. The check reviews only the change, so a pull request that does not touch dependencies passes.
Why Semgrep and code scanning are in evaluate. They are running and their results are visible, but they are not yet blocking. Moving them to active is a decision for the owner once the findings have been reviewed.
Release protection: enterprise-release-tag-protection
Section titled “Release protection: enterprise-release-tag-protection”- Target: tags matching
v[0-9]*.[0-9]*.[0-9]*. - Mode:
active. - Rules: deletion is blocked; force-update is blocked; non-fast-forward updates are blocked. Creating a tag is allowed.
- Bypass: the
bundu-releaseGitHub App only.
Why. A released version must not change after it is published. Anyone can create a version tag, but nobody can move or delete one, and that includes the people who can merge to main. The only exception is the release app, which creates the tags.
Staging protection: enterprise-staging-protection
Section titled “Staging protection: enterprise-staging-protection”- Target: the branch
staging, in every repository. - Mode:
active. - Rules: creation only. Creating a
stagingbranch is restricted. The pull request, linear history, deletion and non-fast-forward rules were removed on 2026-11-21, because there is nothing left to protect. - Bypass: unchanged. Organization admins, for the pull request mode, which now has no rule to apply to; enterprise owners, always; the
bundu-releaseGitHub App, always.
This ruleset exists to stop a staging branch being created again. No repository in bundu-labs has a staging branch, as checked through the API on 2026-11-21, and Bundu’s policy is that none should be created. Enterprise owners and the bundu-release GitHub App can still create one, because their bypass is always on.
Summary of the enterprise rulesets
Section titled “Summary of the enterprise rulesets”| Ruleset | Targets | Mode | Bypass |
|---|---|---|---|
enterprise-main-protection |
Default branch | active | Enterprise owners; organization admins (PRs only) |
enterprise-release-version-check |
Default branch | active | Enterprise owners |
enterprise-dependency-review |
Default branch | active | Enterprise owners |
enterprise-org-workflows |
Default branch | active | Enterprise owners |
enterprise-release-tag-protection |
Tags v* |
active | bundu-release app |
enterprise-staging-protection |
staging |
active | Organization admins (PRs); enterprise owners; bundu-release app |
enterprise-code-scanning |
Default branch | evaluate | Enterprise owners |
enterprise-semgrep |
Default branch | evaluate | Enterprise owners |
enterprise-repo-standards |
Default branch | evaluate | Enterprise owners |