I have a report from one of my colleagues that when they use

gt modify

(which they expect essentially does

git add . && git commit --amend

) on their repo with

pre_commit

hooks (that do some validation), it doesn't correctly run the

pre_commit

how he expects (on the combined code of unstaged changes and whats already been commited before - the branch is single commit created with

gt create

), instead his code switches back to the already commited version as if he did

git stash

(visible when his IDE is open) for like half a second what exactly does

gt modify

do under the hood (for the

--all

option)? is there a way to see commands

gt

executes with

git

under the hood?

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

My colleague just started using Graphite, I am not observing this myself (however I am not working on the same repo as he does) He says it happens only occasionally, not every time, but he has to use

git commit -a --amend

when it happens to workaround it because the

pre_commit

hook keeps failing

Hey Filip, you can see everything happening under the hood by adding the

--debug

 flag to your

gt

commands. Also to be clear, they are running

gt modify -a

 to stage and commit or just

gt modify

?

thanks,

gt modify

and then selecting the first option (I think that's the All)