> ...but Git does not really expect published history to change... That's a weird statement for a tool which has had `rebase` as the very basic command from th

> ...but Git does not really expect published history to change... That's a weird statement for a tool which has had `rebase` as the very basic command from the get go. Git does expect history to change, it's publicised as a solution to a bunch of issues: basically, there is no getting around understanding the Git internals, and even once you do, it's hard to remember how GIT cli commands tie into those internals for things you seldom use because of their arcane naming.