Graphite Community

When I do `gt reorder` and forget that I have staged or unstaged changes, the command aborts due to conflicts and I lose commits in some branches and have to go to reflog to pull them back in.

Could there be a way to warn or abort early without doing any of the git commands in reorder to prevent this? Maybe even just a warning that there are uncommited changes :sweat_smile:

(If applicable) To help us repro, please send the following if you haven't already:
- PR links, screenshots, and/or debug output if applicable
- Repro steps
- Does this happen consistently? Just to you or others on your team also?
- Is this a regression? Is the problem new?
- If you're having an issue with the CLI, please send us debug logs using `gt feedback --with-debug-context &lt;any message&gt;`


Hey Scott, ive seen some older threads on this, let me see if any enhancement requests exist and if not i will write one up. OOC, does `gt undo` work to get you back to the right state?


Hm.. I didn't try `undo` today when it happened but I think I remember trying it the first time this happened and it didn't work. I can try it next time I run into this :sweat_smile: