Engineering overview
Bundu repositories are governed by GitHub rulesets set at three levels: the enterprise, the organization and the repository. A merged change to the default branch is released by a scheduled job. This section describes what is configured today, read from GitHub’s API and from the central workflow repositories. Where a rule is written down but not yet in force, it is marked as planned.
The short version
Section titled “The short version”- Rules are set from the top. The enterprise and the
bundu-labsorganization hold the rules that apply to every repository, so a new repository is covered without setup. - The default branch,
main, accepts changes by pull request only. Changes go through a merge queue, and nobody can force-push or delete the branch. - Each merge to
mainis a release. A scheduled job tags the tip ofmainwith the next version, using the title of the merged pull request: afeatmakes a minor release, anything else a patch. - A breaking change is never tagged automatically. It is released as a major version by a maintainer.
- Version tags (
v*) cannot be moved or deleted.
Pages in this section
Section titled “Pages in this section”- Rulesets overview: what a ruleset is, how the three levels combine, and the full inventory.
- Enterprise rulesets: the floor that applies to every organization.
- Organization rulesets: the required checks and workflows for the
bundu-labsorganization. - Repository rules: what a single repository adds, such as its merge queue.
- How a change gets released: the walkthrough from branch to tag, with a diagram.
- Requesting an exception: how to have a rule bypassed, and who can approve it.
Not covered here
Section titled “Not covered here”- Runner pinning, such as
ubuntu-24.04. It is set per repository. - Application-level deployment. A repository’s own build and deploy setup is documented in that repository.