Masking Email Addresses in Git Commit History

A commit history can betray more than code. It can expose email addresses in plain sight, leaving sensitive data embedded forever in the logs. When teams need to clean this up, git reset alone is not enough — you must rewrite history with intent and precision to mask these addresses without breaking the repository.

Email leakage into Git logs often comes from misconfigured user.name and user.email in local environments, accidental commits with real addresses in code comments, or automated scripts that stamp credentials. These entries persist through clones, mirrors, and backups. Removing them means editing both the commit metadata and any file content containing the addresses.

The most reliable method is to use git filter-repo or git filter-branch to iterate over every commit, detect email patterns, and replace them with an approved placeholder such as masked@example.com. Plain git reset changes branches, but it does not alter past commits. To truly mask email addresses in Git logs:

1. Install git filter-repo for better performance and simpler commands than filter-branch.
2. Run a script to replace commit author and committer email fields with the masked value.
3. Search file diffs for email regex patterns and rewrite those lines.
4. Force-push the rewritten repository to overwrite remote history.

Example with git filter-repo:

git filter-repo --mailmap my-mailmap.txt

Where my-mailmap.txt defines the mapping from real emails to masked addresses. This approach standardizes all occurrences without manually touching each commit.

Masking is not optional when dealing with legal compliance, GDPR, or internal security policies. Leaving addresses in history can expose staff to phishing and harm organizational privacy posture. Once fixed, enforce pre-commit hooks or CI checks that block unapproved email formats from entering the repository again.

See the full workflow live and learn how to sanitize Git histories in minutes with hoop.dev — run the process yourself now and protect your logs before the next clone.