Somewhere between a bug report and a feature reque...
# report-bugs
s
Somewhere between a bug report and a feature request I guess: graphite appears to have started stashing my current worktree state before running a git operation, and popping it back if that operation fails. This messes with my pre-commit hooks since I have a formatter: the formatter formats the file and returns non-zero so I can make sure the formatting is right. I expect to then see the formatting as unstaged changes. But since the git commit (in this case) failed (a pre-commit hook had a nonzero exit code and the commit didn't run), graphite pops from the stash and I lose my formatting. I understand some people might want this behavior, but I don't like it and would want it to be configurable!
✅ 1
p
(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>
hey Sam, we're aware of this one and have a fix in the works that will prevent the pre-commit hook failure from losing the unstaged changes. Look out for it in the coming release!
❤️ 1
The fix for this is out in 1.8.6!
party parrot 1