feat(rawr): add safety checks for Graphite sync with --force#26
Open
mateicanavra wants to merge 2 commits intocodex/integration-upstream-mainfrom
Open
Conversation
Author
This stack of pull requests is managed by Graphite. Learn more about stacking. |
05fa42b to
8af908c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Improve Graphite rebase safety with
--forceflagThis PR enhances our rebase documentation and scripts to address safety concerns when using Graphite commands in non-interactive automation:
gt sync --no-restack --force --no-interactivefor automationrebase-daily.shto verify local/remote trunk alignment before runninggt sync --forceThese changes help prevent potential data loss scenarios where
gt syncmight overwrite local trunk when it cannot fast-forward, especially in CI/automation contexts.