Last updated 22 April 2016.

With all the names, usernames, git usernames, user.names and e-mail around, let's take a look at what they mean and where they appear. username

The username set at which you use to log into is, as far as it relates to Git, displayed:

On the Commitlog


On the View All Committers page

On the Maintainer's block password

Your password, set at, is both your password AND your Git password.

Drupal password

Git password

Git username

The Git username, set permanently at[uid]/edit/git, is used for Git authentication when communicating with the server. This is typically the same as your username, but can be different for older accounts due to historical reasons. You'll see it in:

On the Git access tab

(Needs screenshot)

Clone urls

Password prompt e-mail address(es)

Any e-mail address associated with your account is also a valid choice for a Git e-mail address. Note that while an e-mail address is associated with your account it cannot be used by any other account. These e-mail addresses aren't visible anywhere on, except to you on the "E-mail addresses" tab.


(Your name, just like the "friendly name" displayed on an e-mail.)
This shows with in the normal git commit log locally.

And it shows the repository viewer (without the e-mail).


To get credit for a commit, the e-mail address you use here must match one of the e-mail addresses you've confirmed. This e-mail address will be visible in the repository's git log, but is not exposed to the web (and spam bots) anywhere on In addition, you can choose to use a fake address. The format is [git-username]@[your-uid]


Vacilando’s picture

Can git contain UTF8 characters - or does it have to be in ASCII-coded?

TR’s picture

This e-mail address will be visible in the repository's git log but is not exposed to the web (and spam bots) anywhere on

This is not really true.

If you are a contributor and create patches using the Drupal-recommended* git format-patch, the patch will contain your user name and e-mail address. Any patches you post to the issue queue will be indexed, and your e-mail address will be harvested for spam. If you're not creating patches in the first place, you probably aren't using Git either, so in MOST cases the e-mail address you choose WILL be "exposed to the web (and spam bots)".

If you intend to post patches I strongly suggest using the form [git-username]@[your-uid] for your e-mail address. Or ignore the documentation to use git format-patch and instead use git diff, which won't include your e-mail address.

*The recommendation to use git format-patch is in the Patch contributor guide as well as on the "Version control" tab that shows up on every project page.