Show HN: Git-knife – edit commit messages, authors, and dates like a spreadsheet
Conversation activity · last 31 hours peak 4/30m
Clustered from 12 items across 3 sources. Not yet parsed — the coverage below is the raw record.
Press coverage 1
Social posts 3
Voices from the web unedited
-
One of the most annoying quirks of LLMs for me is the insistence on, after being corrected, loudly noting what wasn't done. After getting it to change something stupid in code, it will leave a comment in the code boasting about how it doesn't do the stupid thing, which to future readers reads like an 'asbestos free!' label on a cereal box.
-
I appreciate that it uses git-notes and that is makes backup branches in it's own namespace. I wish it were a bit lighter though.Haven't seen mentioned, but you might want to check out
-
Note: This will not work and cannot work on repos that use signed commits from multiple authors.Signed git history is immutable, and unsigned git history is a supply chain attack vector.That said I could see this being useful for single-author WIP branches doing cleanup before a PR
-
“It never reimplements git — it shells out to the system git CLI and rebuilds commits with git commit-tree, reusing each commit's original tree so file contents are provably never changed.”Glad the LLM noted this - I was worried this would reimplement git
-
It looks like the screenshot was an actual photo of someone's monitor. I'm left wondering why print screen wasn't utilized. And for some reason it really makes me not want to touch this project.
-
Offtopic but, it always amuses me that the words "provably" and "probably" are one letter apart (and I frequently misread them for each other).
-
Ha ha fair. But yeah shelling out to git and reusing the original tree object was deliberate means file contents can't change even if I screw up elsewhere.