commit
e6efa32ab6a439a0d288907c915dc7ded31c92a1
Author:
Dan Ott <danott@users.noreply.github.com>
Date:
Thu Jan 18 09:10:22 2024 -0500
Reply:
GitHub
Home:
allow-empty
Next:
a2be7ec023cb6920a295bd0381a42a53de628bff
Prev:
7b43b4bfcab94cbb2576783ba7be592b45dc148d

The shame of git push --force

This blog is only 11 posts deep. I’ve learned a few things while writing it.

I wanted to fix some small things in the existing entries. Mostly making sure I adequately linked out to references. And I surrounded bare links with carets so Kramdown will turn them into real anchor tags with an href.

I kicked off this process with a git rebase -i --root. I picked some commits and reworded others. All said and done, the edits are made.

But making these edits changes git history, including the sha of each commit. I’ve been calling it a hash. Should I update that in code that builds the HTML representation?

I’ve created a tag to capture the state before force pushing. Just in case I’ve lost something to history that I might want to resurrect.