You can’t change anything about a commit without breaking the chain of SHA hashes in the commits, which causes pulls to break.
replyGitHub hides the emails on their web UI, but nothing stops people from pulling the repository with a Git client and looking at the emails in the commit log after doing so.
Which is why you should be careful to never use your actual email in git commits.
replyWhen I made a patch to the Linux kernel I did have to use a real email, since you have to send to their mailing list. I used a throwaway email for it, which I have since edited on my mail server config to forward to /dev/null (yes, I'm one of the weirdos still self hosting email in 2026). The amount of spam I got was insane, and not even developer relevant spam.
This makes me wonder how the Linux kernel git system deals with GDPR data deletion requests. Are they even legally allowed to deny them?
replyYou have to configure your own Git client manually. But you can configure GitHub to block pushes from any email other than the no reply email GH generates for you.
reply