There’s not much more github can do about this because of how git works: git commits form a merkle tree (aka blockchain): each commit is a hash of its contents

There’s not much more github can do about this because of how git works: git commits form a merkle tree (aka blockchain): each commit is a hash of its contents (including the author’s email) as well as the entire history to that point. When you commit to a public repo, the email you commit with is publicly visible forever unless a repo owner rewrites history and force pushes. GitHub has an option to create web commits with private non-routable emails and to block pushes you inadvertently attempt which include commits made with your public email that you choose to keep private. Filtering existing emails from the API wouldn’t work since scrapers can just as easily clone the repo, which (by git’s design) cannot be altered without breaking everything. (Disclosure: I am a GitHub employee)