Skip to content
Sarj Repo Standards
sarj/delivery/hotfix-backsync

Back-sync production hotfixes

Production hotfixes automatically flow through preview to development.

error

Examples

FlaggedFails
main -> preview; preview -/-> dev
PassesClean
main -> preview -> dev through guarded pull requests and required CI

Why it matters

A later promotion can reintroduce a production fix that was not back-synced.

How detection works

An active main, preview, and development chain lacks a guarded pull-request back-sync edge or its required repository controls.

What is inspected

  • all three delivery branches exist or are explicitly declared
  • both synchronization edges have guarded pull-request workflow structure
  • live repository settings expose protected branches and required CI

Limits

  • creating branches or workflows
  • merging pull requests
  • automatically resolving merge conflicts

How to fix it

Add idempotent PR-based backsync workflows and protect every long-lived branch.

  1. Implement guarded main-to-preview and preview-to-development pull requests.
  2. Require CI and auto-merge only the verified source commit.

Verify

  • Run repo-lint again and confirm the rule passes.