Skip to content

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.

  • Rules are set from the top. The enterprise and the bundu-labs organization 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 main is a release. A scheduled job tags the tip of main with the next version, using the title of the merged pull request: a feat makes 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.
  • 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.