Temporary email for GitHub

1. Verify an account email you can keep

Use a lasting mailbox for account verification and future account messages. GitHub limits important features until an email is verified, including creating repositories, issues and pull requests.

If you need another verification email, open your profile menu → Settings → Emails, then select Resend verification email beneath the address. Open the link in the received message. These are GitHub’s verification steps; interface labels may change.

2. Use GitHub’s noreply address for commit privacy

In Settings → Emails, enable Keep my email addresses private and copy the GitHub-provided noreply address shown there. Use that exact value rather than guessing its format. GitHub’s web-based commits use noreply when email privacy is enabled; command-line commits need their own Git configuration.

In the local repository where you want this setting, replace the placeholder below with your copied noreply address. The first command changes this repository’s setting; the second reads it back.

git config --local user.email "YOUR_GITHUB_NOREPLY_ADDRESS"
git config --local user.email

GitHub documents web and command-line commit email settings. Git’s local configuration reference explains the repository scope. Your account mailbox and commit-author address serve different purposes: a noreply commit identity does not replace account verification.

3. Check the commit, not just the setting

After making a new local commit, inspect its stored author and committer addresses before pushing:

git show -s --format='Author: %ae%nCommitter: %ce' HEAD

The Git format reference defines these two fields. Changing your configuration affects future commits; it does not rewrite an earlier commit. If the output still shows another address, check the tool or environment that created that commit before publishing it.

GitHub also offers Block command line pushes that expose my email in email settings. It checks the latest commit’s author address against private emails on your account; inspect other commits separately. See the push-blocking documentation. This does not erase addresses already published in repository history.