1user.name:: 2user.email:: 3author.name:: 4author.email:: 5committer.name:: 6committer.email:: 7 The `user.name` and `user.email` variables determine what ends 8 up in the `author` and `committer` field of commit 9 objects. 10 If you need the `author` or `committer` to be different, the 11 `author.name`, `author.email`, `committer.name` or 12 `committer.email` variables can be set. 13 Also, all of these can be overridden by the `GIT_AUTHOR_NAME`, 14 `GIT_AUTHOR_EMAIL`, `GIT_COMMITTER_NAME`, 15 `GIT_COMMITTER_EMAIL` and `EMAIL` environment variables. 16 See linkgit:git-commit-tree[1] for more information. 17 18user.useConfigOnly:: 19 Instruct Git to avoid trying to guess defaults for `user.email` 20 and `user.name`, and instead retrieve the values only from the 21 configuration. For example, if you have multiple email addresses 22 and would like to use a different one for each repository, then 23 with this configuration option set to `true` in the global config 24 along with a name, Git will prompt you to set up an email before 25 making new commits in a newly cloned repository. 26 Defaults to `false`. 27 28user.signingKey:: 29 If linkgit:git-tag[1] or linkgit:git-commit[1] is not selecting the 30 key you want it to automatically when creating a signed tag or 31 commit, you can override the default selection with this variable. 32 This option is passed unchanged to gpg's --local-user parameter, 33 so you may specify a key using any method that gpg supports.