Skip to main content
Royal Glow uses one platform release train across the complete monorepo. Work starts on a short-lived branch from dev and moves through dev -> test -> pprd -> prod using pull requests.

​
Change lifecycle

  1. Branch from the latest dev and use Conventional Commits.
  2. Open a pull request into dev and resolve review and automated checks.
  3. Add merge-ready when the pull request is approved for the Mergify queue.
  4. Promote dev -> test, test -> pprd, and pprd -> prod with dedicated PRs.
  5. Release Please records changes already on prod in one platform release.
  6. Merge a reviewed prod -> dev release-sync PR before the next promotion cycle.
Feature and Release Please PRs use squash merges. Promotions and release sync use merge commits to retain shared ancestry and the original feature history. Mergify is the only merge orchestrator. GitHub’s native merge queue and native auto-merge must remain disabled. GitHub Rulesets supply the non-bypassable baseline; Mergify adds queue ordering, branch progression, and freeze controls.

​
Ownership map

See CI/CD, GitHub Rulesets, and Release Process.
Last modified on September 6, 2026

Related topics

Git WorkflowRelease ProcessCI/CDPlatform Implementation ReportSecurity And Coverage