use-graphite

Graphite manages large changes by splitting them into a sequence of dependent PRs, guiding you to use Graphite-aware commands like gt create and gt submit instead of standard git push. This maintains a clean, reviewable PR stack for incremental development.

Git push and gh pr create are blocked because the Graphite workflow intercepts conflicting git and gh commands to prevent unreviewable pushes. It guides you to Graphite-safe alternatives like gt submit to maintain stack alignment in a Graphite-managed repository.

Graphite-safe alternatives include using gt create to start new branches and gt submit for creating PRs. These commands replace git branch and gh pr create, ensuring actions remain stack-aligned and prevent conflicts within a Graphite-managed repository.

Yes, you need the Graphite CLI and its repository configuration to manage stacked PRs. The workflow relies on the Graphite CLI to intercept standard git and gh commands, providing safe, stack-aligned actions for large feature migrations and refactors.

You should use stacked PRs for large features, migrations, or refactors that would otherwise be unreviewable as a single pull request. Graphite enables incremental development by managing these large changes as a sequence of dependent PRs.