Organization rulesets
The organization ruleset, org-wide-main-protection, is set on the bundu-labs organization. It targets the default branch of every repository except those whose names begin with sandbox- or archive-. It is the layer that decides whether a pull request can merge, on top of the enterprise floor.
| Rule | Setting |
|---|---|
| Required status checks | Seven contexts, listed below. Not required to be up to date with the base branch. |
| Required workflows | bundu-labs/.github: org-lint.yml and all-checks-green.yml, on main. |
| Pull request | Required. 0 approving reviews. Review threads must be resolved. No code owner review required. |
| Allowed merge methods | Merge, rebase and squash. |
| Deletion | Blocked. |
| Force-push | Blocked. |
| Bypass | Organization admins, always. |
The seven required status checks
Section titled “The seven required status checks”These checks come from the org-lint.yml required workflow, which runs on every pull request.
lint / actionlint: the GitHub Actions workflow files are valid.lint / markdownlint: Markdown follows the rules in the repository’s.markdownlint.jsonc.lint / yamllint: YAML files follow the repository’s.yamllint.yaml.vite-plus / fmt: formatting passes.vite-plus / check: type checking and linting pass.vite-plus / test: the tests pass.vite-plus / build: the project builds.
The two required workflows
Section titled “The two required workflows”org-lint.ymlruns the lint and Vite+ jobs above, plus theissue attachedcheck (a pull request must close or reference an issue, or sayNo issue: <reason>) and theno agent-local filescheck (a pull request must not addCLAUDE.mdor.claude/). Its jobs call reusable workflows innyuchi/.githubpinned to a commit.all-checks-green.ymlis the gate that waits for every other check on the commit. It fails if any check is red, cancelled or timed out. It keeps waiting while a check is pending, for up to 40 minutes. It is required by the workflow rule rather than as a status check name, so it is not in the list of seven.
Why each rule
Section titled “Why each rule”Pull request, with 0 approvals. The approval count follows the solo-developer phase described in the enterprise page. Review threads must be resolved before merging.
Required status checks. Lint and build must pass before a change reaches main. They are named contexts, so a failing one is shown by name on the pull request.
Required workflows. org-lint.yml is required so that the lint gate runs in every repository without each one needing its own copy. all-checks-green.yml is required so that checks outside the list above, such as CodeQL, dependency review and Semgrep, can still block a merge. A check that is red anywhere on the commit fails the gate.
Not up to date with the base branch. The merge queue tests each entry against the latest main before it lands. The written standard says this setting should be on; it is off in the live ruleset. The difference is listed in the overview.
Deletion and force-push blocked. A force-push can move a branch away from the commits a release was tagged on, and a deletion removes the branch. Both are blocked on main here and at the enterprise level.
Merge methods. The organization allows merge, rebase and squash. The merge queue on a repository sets the method that queue uses; see repository rules.
Bypass
Section titled “Bypass”Organization admins can bypass every rule in this ruleset, always. The bypass is not used for ordinary merges. See requesting an exception before using it.