stacked-pr-workflow

Manage stacked PR workflows by inspecting current branch states and boundaries, then applying operations like restack, reparent, or squash to maintain clean, ordered, and ready PR chains.

The best way to restack interdependent git branches is using git-spice commands to validate PR boundaries and apply controlled mutations, ensuring clean boundaries and preventing confusing history.

Yes, you can squash branches in a stacked PR chain before submission. The workflow validates PR boundaries and applies guardrails to ensure mutations are controlled and safe.

Yes, the stacked PR workflow supports local git workflows involving multiple interdependent PRs, allowing you to inspect, track, reparent, and submit branches in a guardrailed manner.

Validating PR boundaries in a stacked git workflow prevents boundary leakage and confusing history when multiple related branches are drafted, reviewed, and submitted in a sequence.

You should avoid automated mutations on stacked PRs when destructive actions require confirmation, as the workflow enforces guardrails to prevent unintended branch history changes.