This message was deleted.

I was able to fix my issue by finding the commit that was erased by Graphite using

git reflog

➕ for using

reflog

when in doubts about commit history

Is there an easy way to figure out where I went wrong? I am surprised how easily I scuffed this up... This is my first time using Graphite. I'm not a wizard by any means, but I am bit surprised how easily I was able to make Graphite delete things from git and cover its tracks

I'm certainly not a wizard either! much more of a new user. but my take would be, Graphite is built on top of git. I think it could be described as an opinionated set of git practices. And force-pushing to amend commits is a core mechanism, it's used in lots of

gt ...

operations. So I don't think you are going to be able to configure Graphite not to force-push. But, do note that you can still use standard

git

operations, if those are more comfortable for you. So, you can

git commmit -am "my awesome changeset"

and it will compose fine with Graphite stacks. I was very much not in the habit of force-pushing, until I started using Graphite, so I feel you on this one. Note that after force-pushing, the result is generally a new commit which replaces the old one.

Thanks for the perspective