Skip to main content

Cross-Repo Branch Promotion Policy

This policy standardizes how API, mobile, and service changes move into beta so every developer uses the same path.

Accepted Source Branch Prefixes​

Use one of these prefixes for work intended to promote into beta:

  • feature/*
  • refactor/*
  • fix/*
  • chore/*
  • hotfix/*

Promotion Path​

  1. Push source branch (for example feature/driver-load-status).
  2. CI validates the branch and opens an automated PR to beta.
  3. Team reviews and merges PR into beta.
  4. Environment-specific deployment/update runs from beta.

Platform Notes​

  • API and service also support staging/* for direct alpha promotions when needed.
  • Mobile uses build/* for native build intent branches. These are not beta promotion branches.

Team Guardrails​

  • Do not push deployment changes directly to beta, alpha, or main unless explicitly planned.
  • Keep commit messages clear and include [no deploy] only when intentionally skipping deployment jobs.
  • Verify branch naming before push to avoid bypassing automation.