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
- Branch from the latest
dev and use Conventional Commits.
- Open a pull request into
dev and resolve review and automated checks.
- Merge once the pull request is approved and the required checks report success.
- Promote
dev -> test, test -> pprd, and pprd -> prod with dedicated PRs.
- Release Please records changes already on
prod in one platform release.
- 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.
GitHub Rulesets are the only merge gate and supply the non-bypassable baseline.
There is no third-party merge orchestrator: merges are performed directly once a
pull request is approved and its required checks succeed. Queue ordering,
priorities, and merge freezes are not configured; if serialized merges become
necessary, enable GitHub’s native merge queue rather than reintroducing an
external service.
Ownership map
See CI/CD, GitHub Rulesets, and
Release Process. Last modified on September 22, 2026
