cross-repo-backporting

What problem does it solve?

Cross-repo backporting prevents fleet-wide drift by defining what must stay consistent across sibling SaaS products and how to safely propagate changes without accidentally forking behavior or corrupting shared data.

Core Features & Use Cases

• Classify changes as core vs product-specific so you know what must be synchronized (auth, RLS, billing/credits, pipelines, observability) versus what should intentionally diverge (brand, prompts, copy, product-only tables).
• Canonical-product-first backport workflow that lands and burns in the change on a single canonical repo, then diffs, adapts, and backports to siblings with one PR per repo while tracking a propagation ledger.
• Schema migration coordination and safety rules for shared tables, including author-once in the canonical product, verbatim copying, sequential numbering per product, and strict “never edit shipped migrations” guidance.

Quick Start

Ask your agent to backport a fleet change by first selecting the canonical product, then diffing touched backbone files across each sibling, and finally producing one scoped backport PR per sibling with documented adaptations and drift findings.