Tools like git-filter-repo[1] support rewriting commit hashes in commit messages. git-filter-repo actually does it by default; see `--preserve-commit-hashes` in the manual[2].

[1]: https://github.com/newren/git-filter-repo

[2]: https://htmlpreview.github.io/?https://github.com/newren/git...

▲

donatj 9 hours ago | parent | next [-]

Sure, but that's not going to rewrite Slack messages, emails, GitHub links, docs

▲

purpleidea 9 hours ago | parent | next [-]

Came to say something exactly like this... The old sha1 handle needs to be still available in the same way an HTTP 301 redirect would work.

▲

diegocg 9 hours ago | parent | prev [-]

... do not migrate old repos? I'm not sure why people would do that. Or, if they do, why would they replace the current repo name instead of creating a different one and keeping the old one closed to make the references work.

I don't think this is going to be a problem at all.

	▲	beart 6 hours ago \| parent [-]
		Hmm. If this is a security issue that matters, would you not be expected to migrate? Not talking about archived code, but active projects that pre-date git 3.0

▲

okanat 4 hours ago | parent | prev [-]

I need git-filter-repo to rewrite entire documentation and also resurrect and rehire earlier employees to repeat their GPG signatures.