Hi, When running

gt modify

without

-m

the vim editor opens. A couple of people in my team have had an issue where aborting that will delete changes that were staged.

ERROR: Failed to roll back {"exitCode":1,"name":"CommandFailed"}ERROR: Command failed with error exit code 1:git commit -q

I know we can recover files with

git fsck --lost-found

however this is a workaround for a graphite bug. We are quite concerned about this and I was told that this is a known issue, is there any progress on this?

(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 <any message>

This happened 5 weeks ago to me and someone in my team had it happen to them today

Hey Jack just responded to you in your original report. This is not actively being worked on unfortunately. have added a note to the ticket that you continue to hit this.

Is there anything we can do to avoid losing our work from this bug? Is there a way to make it not open vim or anything else that would help us other than relying on the lost found git feature?

i think the safest bet is using

-m "message"

. One thing looking back, your initial report was re:

gt create

which needs a message whereas

gt modify

assuming not on an empty branch would not need one since it amends and keeps the existing message. in either case using

-m

flag would prevent the vim and any empty commit messages