GitHub Enterprise uses the email address set in your local Git configuration to associate commits pushed from the command line with your GitHub Enterprise account.
You can use the git config
command to change the email address you associate with your Git commits. The new email address you set will be visible in any future commits you push to GitHub Enterprise from the command line. Any commits you made prior to changing your commit email address are still associated with your previous email address.
For more information on commit email addresses, see "About commit email addresses."
Setting your email address for every repository on your computer
Open TerminalTerminalGit Bash.
-
Set an email address in Git. You can use any email address.
git config --global user.email "email@example.com"
-
Confirm that you have set the email address correctly in Git:
git config --global user.email email@example.com
Add the email address to your GitHub Enterprise account by setting your commit email address on GitHub, so that your commits are attributed to you and appear in your contributions graph.
Setting your email address for a single repository
You can change the email address associated with commits you make in a single repository. This will override your global Git config settings in this one repository, but will not affect any other repositories.
Open TerminalTerminalGit Bash.
Change the current working directory to the local repository where you want to configure the email address that you associate with your Git commits.
-
Set an email address in Git. You can use any email address.
git config user.email "email@example.com"
-
Confirm that you have set the email address correctly in Git:
git config user.email email@example.com
Add the email address to your GitHub Enterprise account by setting your commit email address on GitHub, so that your commits are attributed to you and appear in your contributions graph.
Further reading
- "About commit email addresses"
- "Setting your commit email address on GitHub"
- "Git Configuration" from the Pro Git book