The Git history command deserves more attention

Re:The Git history command deserves more attention by chandlerswift on Monday July 13, 2026 @11:52PM (#48902112)

I've been theoretically a big fan of these commands; I use the `jj` equivalents all the time. The roadblock I've run into is that I as far as I can tell (from the man pages and the git source code) there's no way to get `git history` commands to sign commits they modify:

    $ git log --oneline --show-signature  # look ma, I signed my commits!
    3a1dd8f gpg: Signature made Mon 13 Jul 2026 10:45:50 PM CDT
    gpg:                using RSA key FBF32CDBCC134B44FD29B66FA851D929D52FB93F
    gpg:                issuer "[email protected]"
    gpg: Good signature from "Chandler Swift <[email protected]>" [ultimate]
    Second commit
    03c3f6e gpg: Signature made Mon 13 Jul 2026 10:45:16 PM CDT
    gpg:                using RSA key FBF32CDBCC134B44FD29B66FA851D929D52FB93F
    gpg:                issuer "[email protected]"
    gpg: Good signature from "Chandler Swift <[email protected]>" [ultimate]
    Initial commit
    $ git history reword HEAD~
    $ git log --oneline --show-signature  # oops! where'd they go?
    5662b2c (HEAD -> main) Second commit
    6bf6830 Initial commit amended

This has pushed me back to the time-honored `git rebase -i` since I do want to keep my commits signed.

[ Parent | on HN ]

Re:The Git history command deserves more attention by jmholla on Tuesday July 14, 2026 @01:34AM (#48902663)

Woah! That feels like a huge oversight and like it bypasses standard commit logic. The man pages do say `git history` is experimental. Sounds worth a bug report.

[ Parent | on HN ]