MokoGIT: Branch Model & Release Channels

Details
Category: Guides
  • Applicable Software: MokoGIT
  • Min Version Number: 02.09.00
  • Max Version Number: Not Applicable

Overview

MokoGIT's own platform repositories use a channel-named branch model: each long-lived branch is named for the release channel it represents. Instead of a single main branch, work flows up a promotion ladder of named branches, and the top of the ladder is the production/default branch.

The ladder: dev → rc → stable

  • dev — the development channel. Feature and fix branches merge here first; this is where changes are integrated and validated.
  • rc — the release-candidate channel. Content promoted from dev is staged here for release-candidate testing.
  • stable — the production channel and the repository's default branch. Only content that has passed the rc gate is promoted here, and promotion to stable is what cuts a stable release.

Changes always move up the ladder by promotion (never straight to stable), so every stable release has already been integrated on dev and tested on rc.

What changed (and why)

MokoGIT's production/default branch was renamed from main to stable so the branch name matches the release channel it serves. This makes the ladder self-describing: the branch you are on tells you which channel your code is in. Feature work still happens on short-lived feature/*, fix/*, and chore/* branches that open pull requests into dev.

Branches and tags can share a name

Because branches are named for channels, a release tag can share the name of a branch. For example, a repository can have a long-lived stable branch and also publish a stable release tag; MokoGIT keeps the two distinct (a branch ref vs. a tag ref) even though they share a label. This is expected and supported.

Most repositories still use main

The channel-named model applies to MokoGIT's platform repositories. Most other repositories still use a conventional main default branch, and that is fully supported — you do not have to adopt channel-named branches for your own projects. Platform workflows are written to recognize both conventions, so shared CI/CD behaves correctly whether a repository's default branch is stable or main.

Related

See MokoGIT: CI/CD & Release Pipeline for how the shared workflows build and release from each branch, MokoGIT: Cascade Merge Rules for how promoted content flows back down the ladder, and MokoGIT: Branch Protection & Organization Governance for protecting these branches.

Get help

Open a support ticket or call (931) 279-6313.

Hits: 5