Changing git history is simply and utterly wrong unless you are the sole developer, for the reasons you already understand. I would even go so far as to say th

Changing git history is simply and utterly wrong unless you are the sole developer, for the reasons you already understand. I would even go so far as to say that even with a sole developer, this shouldn't be part of a workflow, as 1 developer can become 2 fairly easily. I think you need to mention this in your homepage/video/marketing somewhere. You're basically making it easier to mutate Git history, with all the concurrency issues that that creates. The reason why changing history in Git is hard, is because it should be hard.