blocks|key|2104574|text|您可以将单个存储库配置为使用覆盖全局配置的特定用户/电子邮件地址。从repo的根目录中，运行|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2104575|git+config+user.name+"Your+Name+Here"
git+config+user.email+your@email.com|code-block|syntax|javascript|2104576|而默认用户/电子邮件是在~/.gitconfig中配置的|2104577|git+config+--global+user.name+"Your+Name+Here"
git+config+--global+user.email+your@email.com|2104578|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

You can configure an individual repo to use a specific user / email address which overrides the global configuration. From the root of the repo, run

<pre><code>git config user.name "Your Name Here"
git config user.email your@email.com
</code></pre>

whereas the default user / email is configured in your ~/.gitconfig

<pre><code>git config --global user.name "Your Name Here"
git config --global user.email your@email.com
</code></pre>

blocks|key|20933|text|从git+2.13开始，可以使用新引入的Conditional+includes来解决这个问题。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|20934|举个例子：|20935|全局配置~/.gitconfig|20936|[user]
++++name+=+John+Doe
++++email+=+john@doe.tld

[includeIf+"gitdir:~/work/"]
++++path+=+~/work/.gitconfig|code-block|syntax|javascript|20937|工作特定配置~/+Work+/.gitconfig|20938|[user]
++++email+=+john.doe@company.tld|20939|20940|请记住，在顶部，[includeIf...]应该遵循默认的[user]。|CODE|20941|entityMap|0|LINK|mutability|MUTABLE|url|https://git-scm.com/docs/git-config#_conditional_includes^0|5|4|K|K|0|0|0|0|0|0|0|0|8|E|T|6|0^^$0|@$1|2|3|4|5|6|7|14|8|@$9|15|A|16|B|C]]|D|@$9|17|A|18|1|19]]|E|$]]|$1|F|3|G|5|6|7|1A|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|1B|8|@]|D|@]|E|$]]|$1|J|3|K|5|L|7|1C|8|@]|D|@]|E|$M|N]]|$1|O|3|P|5|6|7|1D|8|@]|D|@]|E|$]]|$1|Q|3|R|5|L|7|1E|8|@]|D|@]|E|$M|N]]|$1|S|3|-4|5|6|7|1F|8|@]|D|@]|E|$]]|$1|T|3|U|5|6|7|1G|8|@$9|1H|A|1I|B|V]|$9|1J|A|1K|B|V]]|D|@]|E|$]]|$1|W|3|-4|5|6|7|1L|8|@]|D|@]|E|$]]]|X|$Y|$5|Z|10|11|E|$12|13]]]]

Since git 2.13, it is possible to solve this using newly introduced <a href="https://git-scm.com/docs/git-config#_conditional_includes" rel="noreferrer">Conditional includes</a>.
An example:
Global config ~/.gitconfig
<pre><code>[user]
 name = John Doe
 email = john@doe.tld

[includeIf &quot;gitdir:~/work/&quot;]
 path = ~/work/.gitconfig
</code></pre>
Work specific config ~/work/.gitconfig
<pre><code>[user]
 email = john.doe@company.tld
</code></pre>
<hr />
Remember that <code>[includeIf...]</code> should follows default <code>[user]</code> at the top.

blocks|key|3685647|text|或者，您可以在本地.git/config文件中添加以下信息|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3685648|[user]++
++++name+=+Your+Name
++++email+=+your.email@gmail.com|code-block|syntax|javascript|3685649|entityMap^0|9|B|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|P|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|L|$]]

Or you can add following information in your local <code>.git/config</code> file

<pre><code>[user] 
 name = Your Name
 email = your.email@gmail.com
</code></pre>

blocks|key|1361959|text|One命令github帐户交换机|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1361960|此解决方案采用单个git别名的形式。执行后，当前项目用户将附加到另一个帐户|1361961|生成ssh密钥|1361962|ssh-keygen+-t+rsa+-C+"rinquin.arnaud@gmail.com"+-f+'/Users/arnaudrinquin/.ssh/id_rsa'

[...]

ssh-keygen+-t+rsa+-C+"arnaud.rinquin@wopata.com"+-f+'/Users/arnaudrinquin/.ssh/id_rsa_pro'|code-block|syntax|javascript|1361963|将它们链接到您的GitHub+/+Bitbucket帐户|1361964|1361965|copy+default+public+key+pbcopy+<+~/.ssh/id_rsa_pro.pub|ordered-list-item|CODE|1361966|repeat+to+your+GitHub+account|1361967|将密钥粘贴到add+SSH+key+github页面|1361968|copy+other+public+key+|1361969|并调整步骤2至4|1361970|步骤1.自动切换ssh密钥。|1361971|我们可以根据host将ssh配置为使用特定的加密密钥发送。好的是，同一个hostname可以有多个别名。|1361972|请参阅此示例~/.ssh/config文件：|1361973|#+Default+GitHub
Host+github.com
++HostName+github.com
++User+git
++IdentityFile+~/.ssh/id_rsa

#+Professional+github+alias
Host+github_pro
++HostName+github.com
++User+git
++IdentityFile+~/.ssh/id_rsa_pro|1361974|git远程配置|1361975|现在，您可以通过git@github_pro更改git@github.com在git远程中使用这些别名。|1361976|您可以更改现有项目的远程(使用类似git+remote+set-url+origin+git@github_pro:foo/bar.git的东西)，也可以在克隆它们时直接调整它们。|1361977|git+clone+git@github.com:ArnaudRinquin/atom-zentabs.git|1361978|使用别名的，它变成：|1361979|git+clone+git@github_pro:ArnaudRinquin/atom-zentabs.git|1361980|步骤2.更改git+user.email|1361981|Git配置设置可以是全局的，也可以是每个项目的。在我们的例子中，我们想要一个每个项目的设置。更改它非常容易：|1361982|git+config+user.email+'arnaud.rinquin@wopata.com'|1361983|虽然这很容易，但这需要我们对开发人员的渴望。我们可以为它写一个非常简单的git别名。|1361984|我们将把它添加到~/.gitconfig文件中。|1361985|[user]
++++name+=+Arnaud+Rinquin
++++email+=+rinquin.arnaud@gmail.com

...

[alias]
++++setpromail+=+"config+user.email+'arnaud.rinquin@wopata.com'"|1361986|然后，我们所要做的就是git+setpromail让我们的电子邮件只为这个项目改变。|1361987|步骤3.请使用一个命令开关？！|1361988|使用一个没有参数的命令从默认帐户切换到指定帐户不是很好吗？这绝对是可能的。此命令有两个步骤：|1361989|1361990|更改当前项目远程到选定的aliases|unordered-list-item|1361991|change当前项目配置|1361992|1361993|对于第二步，我们已经有了一个单一命令的解决方案，但第一个要难得多。一条命令远程主机更改|1361994|下面是另一个要添加到~/.gitconfig中的git+alias命令形式的解决方案|1361995|[alias]
++changeremotehost+=+!sh+-c+\"git+remote+-v+%7C+grep+'$1.*fetch'+%7C+sed+s/..fetch.//+%7C+sed+s/$1/$2/+%7C+xargs+git+remote+set-url\"|1361996|这允许将所有远程从一个主机更改到另一个主机(别名)。请参见示例：|1361997|$+>+git+remote+-v
origin++git@github.com:ArnaudRinquin/arnaudrinquin.github.io.git+(fetch)
origin++git@github.com:ArnaudRinquin/arnaudrinquin.github.io.git+(push)

$+>+git+changeremotehost+github.com+github_pro

$+>+git+remote+-v
origin++git@github_pro:ArnaudRinquin/arnaudrinquin.github.io.git+(fetch)
origin++git@github_pro:ArnaudRinquin/arnaudrinquin.github.io.git+(push)|1361998|将它们全部组合在一起|1361999|我们现在只需将这两个命令合并为一个命令，这非常简单。看看我是如何集成bitbucket主机交换的。|1362000|[alias]
++changeremotehost+=+!sh+-c+\"git+remote+-v+%7C+grep+'$1.*fetch'+%7C+sed+s/..fetch.//+%7C+sed+s/$1/$2/+%7C+xargs+git+remote+set-url\"
++setpromail+=+"config+user.email+'arnaud.rinquin@wopata.com'"
++gopro+=+!sh+-c+\"git+changeremotehost+github.com+github_pro+&&+git+changeremotehost+bitbucket.com+bitbucket_pro+&&+git+setpromail\"|1362001|Source+Link+-Github|1362002|Source+Link+-Tutorial|1362003|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/ArnaudRinquin/blog/blob/master/2014-03-11-one-command-github-account-switch.md|1|http://arnaudrinquin.github.io/worflow/2014/03/11/fast-github-account-switch/^0|0|G|0|0|0|7|0|0|0|S|0|0|O|U|0|0|6|B|0|0|0|0|E|0|6|4|B|3|10|8|0|6|D|0|0|0|7|0|8|E|O|E|0|H|1G|0|0|5|5|0|0|1J|0|0|K|0|0|0|0|8|C|0|0|B|E|0|0|F|0|0|0|0|0|0|0|A|C|0|0|0|0|0|A|0|0|0|0|J|0|0|0|L|1|0^^$0|@$1|2|3|4|5|6|7|36|8|@$9|37|A|38|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|39|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|3A|8|@$9|3B|A|3C|B|C]]|D|@]|E|$]]|$1|J|3|K|5|L|7|3D|8|@]|D|@]|E|$M|N]]|$1|O|3|P|5|6|7|3E|8|@$9|3F|A|3G|B|C]]|D|@]|E|$]]|$1|Q|3|-4|5|6|7|3H|8|@]|D|@]|E|$]]|$1|R|3|S|5|T|7|3I|8|@$9|3J|A|3K|B|U]]|D|@]|E|$]]|$1|V|3|W|5|T|7|3L|8|@]|D|@]|E|$]]|$1|X|3|Y|5|T|7|3M|8|@$9|3N|A|3O|B|U]]|D|@]|E|$]]|$1|Z|3|10|5|T|7|3P|8|@]|D|@]|E|$]]|$1|11|3|12|5|6|7|3Q|8|@]|D|@]|E|$]]|$1|13|3|14|5|6|7|3R|8|@$9|3S|A|3T|B|C]]|D|@]|E|$]]|$1|15|3|16|5|6|7|3U|8|@$9|3V|A|3W|B|U]|$9|3X|A|3Y|B|U]|$9|3Z|A|40|B|U]]|D|@]|E|$]]|$1|17|3|18|5|6|7|41|8|@$9|42|A|43|B|U]]|D|@]|E|$]]|$1|19|3|1A|5|L|7|44|8|@]|D|@]|E|$M|N]]|$1|1B|3|1C|5|6|7|45|8|@$9|46|A|47|B|C]]|D|@]|E|$]]|$1|1D|3|1E|5|6|7|48|8|@$9|49|A|4A|B|U]|$9|4B|A|4C|B|U]]|D|@]|E|$]]|$1|1F|3|1G|5|6|7|4D|8|@$9|4E|A|4F|B|U]]|D|@]|E|$]]|$1|1H|3|1I|5|L|7|4G|8|@]|D|@]|E|$M|N]]|$1|1J|3|1K|5|6|7|4H|8|@$9|4I|A|4J|B|C]]|D|@]|E|$]]|$1|1L|3|1M|5|6|7|4K|8|@$9|4L|A|4M|B|U]]|D|@]|E|$]]|$1|1N|3|1O|5|6|7|4N|8|@$9|4O|A|4P|B|C]]|D|@]|E|$]]|$1|1P|3|1Q|5|6|7|4Q|8|@]|D|@]|E|$]]|$1|1R|3|1S|5|L|7|4R|8|@]|D|@]|E|$M|N]]|$1|1T|3|1U|5|6|7|4S|8|@]|D|@]|E|$]]|$1|1V|3|1W|5|6|7|4T|8|@$9|4U|A|4V|B|U]]|D|@]|E|$]]|$1|1X|3|1Y|5|L|7|4W|8|@]|D|@]|E|$M|N]]|$1|1Z|3|20|5|6|7|4X|8|@$9|4Y|A|4Z|B|U]]|D|@]|E|$]]|$1|21|3|22|5|6|7|50|8|@$9|51|A|52|B|C]]|D|@]|E|$]]|$1|23|3|24|5|6|7|53|8|@]|D|@]|E|$]]|$1|25|3|-4|5|6|7|54|8|@]|D|@]|E|$]]|$1|26|3|27|5|28|7|55|8|@]|D|@]|E|$]]|$1|29|3|2A|5|28|7|56|8|@]|D|@]|E|$]]|$1|2B|3|-4|5|6|7|57|8|@]|D|@]|E|$]]|$1|2C|3|2D|5|6|7|58|8|@]|D|@]|E|$]]|$1|2E|3|2F|5|6|7|59|8|@$9|5A|A|5B|B|U]]|D|@]|E|$]]|$1|2G|3|2H|5|L|7|5C|8|@]|D|@]|E|$M|N]]|$1|2I|3|2J|5|6|7|5D|8|@]|D|@]|E|$]]|$1|2K|3|2L|5|L|7|5E|8|@]|D|@]|E|$M|N]]|$1|2M|3|2N|5|6|7|5F|8|@$9|5G|A|5H|B|C]]|D|@]|E|$]]|$1|2O|3|2P|5|6|7|5I|8|@]|D|@]|E|$]]|$1|2Q|3|2R|5|L|7|5J|8|@]|D|@]|E|$M|N]]|$1|2S|3|2T|5|6|7|5K|8|@]|D|@$9|5L|A|5M|1|5N]]|E|$]]|$1|2U|3|2V|5|6|7|5O|8|@]|D|@$9|5P|A|5Q|1|5R]]|E|$]]|$1|2W|3|-4|5|6|7|5S|8|@]|D|@]|E|$]]]|2X|$2Y|$5|2Z|30|31|E|$32|33]]|34|$5|2Z|30|31|E|$32|35]]]]

One command github accounts switch
This solution takes the form of a single git alias. Once executed, the current project user will be attached to another account
Generate ssh keys
<pre><code>ssh-keygen -t rsa -C &quot;rinquin.arnaud@gmail.com&quot; -f '/Users/arnaudrinquin/.ssh/id_rsa'

[...]

ssh-keygen -t rsa -C &quot;arnaud.rinquin@wopata.com&quot; -f '/Users/arnaudrinquin/.ssh/id_rsa_pro'
</code></pre>
Link them to your GitHub / Bitbucket accounts
<ol>
<li>copy default public key <code>pbcopy &lt; ~/.ssh/id_rsa.pub</code></li>
<li>login to your GitHub acount</li>
<li>paste the key in the <code>add SSH key</code> github page</li>
<li>copy other public key <code>pbcopy &lt; ~/.ssh/id_rsa_pro.pub</code></li>
<li>repeat and adapt steps 2 to 4 for every other account</li>
</ol>
Step 1. Automatic ssh key switching.
We can configure <code>ssh</code> to send a use a specific encryption key depending on the <code>host</code>. The nice thing is that you can have several aliases for the same <code>hostname</code>.
See this example <code>~/.ssh/config</code> file:
<pre><code># Default GitHub
Host github.com
 HostName github.com
 User git
 IdentityFile ~/.ssh/id_rsa

# Professional github alias
Host github_pro
 HostName github.com
 User git
 IdentityFile ~/.ssh/id_rsa_pro
</code></pre>
git remote configuration
You can now use these aliases in the git remotes by changing <code>git@github.com</code> by <code>git@github_pro</code>.
You can either change your existing projects remotes (using something like <code>git remote set-url origin git@github_pro:foo/bar.git</code>) or adapt them directly when cloning them.
<pre><code>git clone git@github.com:ArnaudRinquin/atom-zentabs.git
</code></pre>
using alias, it become:
<code>git clone git@github_pro:ArnaudRinquin/atom-zentabs.git</code>
Step 2. Changing git user.email
Git config settings can be global or per project. In our case, we want a per project settings. It is very easy to change it:
<pre><code>git config user.email 'arnaud.rinquin@wopata.com'
</code></pre>
While this is easy, it takes way to long for the developers we are. We can write a very simple git alias for that.
We are going to add it to the <code>~/.gitconfig</code> file.
<pre><code>[user]
 name = Arnaud Rinquin
 email = rinquin.arnaud@gmail.com

...

[alias]
 setpromail = &quot;config user.email 'arnaud.rinquin@wopata.com'&quot;
</code></pre>
Then, all we have to do is <code>git setpromail</code> to have our email changed for this project only.
Step 3. One command switch please?!
Wouldn’t it be nice to switch from default account to a specified one with a single parameter-less command? This is definitely possible. This command will have two steps:
<ul>
<li>change current project remotes to the chosen aliases</li>
<li>change current project user.email config</li>
</ul>
We already have a one command solution for the second step, but the first one is way harder.
One command remote host change
Here comes the solution in the form of another git alias command to add to your <code>~/.gitconfig</code>:
<pre><code>[alias]
 changeremotehost = !sh -c \&quot;git remote -v | grep '$1.*fetch' | sed s/..fetch.// | sed s/$1/$2/ | xargs git remote set-url\&quot;
</code></pre>
This allows changing all remotes from one host to another (the alias). See the example:
<pre><code>$ &gt; git remote -v
origin git@github.com:ArnaudRinquin/arnaudrinquin.github.io.git (fetch)
origin git@github.com:ArnaudRinquin/arnaudrinquin.github.io.git (push)

$ &gt; git changeremotehost github.com github_pro

$ &gt; git remote -v
origin git@github_pro:ArnaudRinquin/arnaudrinquin.github.io.git (fetch)
origin git@github_pro:ArnaudRinquin/arnaudrinquin.github.io.git (push)
</code></pre>
Combine them all
We now just have to combine the two commands into one, this is quite easy. See how I also integrate bitbucket host switching.
<pre><code>[alias]
 changeremotehost = !sh -c \&quot;git remote -v | grep '$1.*fetch' | sed s/..fetch.// | sed s/$1/$2/ | xargs git remote set-url\&quot;
 setpromail = &quot;config user.email 'arnaud.rinquin@wopata.com'&quot;
 gopro = !sh -c \&quot;git changeremotehost github.com github_pro &amp;&amp; git changeremotehost bitbucket.com bitbucket_pro &amp;&amp; git setpromail\&quot;
</code></pre>
<a href="https://github.com/ArnaudRinquin/blog/blob/master/2014-03-11-one-command-github-account-switch.md" rel="noreferrer">Source Link -Github</a>
<a href="http://arnaudrinquin.github.io/worflow/2014/03/11/fast-github-account-switch/" rel="noreferrer">Source Link -Tutorial</a>

blocks|key|3685687|text|在从Orr+Sella's+blog+post获得一些灵感之后，我编写了一个预提交挂钩(驻留在~/.git/templates/hooks中)，它将根据本地存储库的./.git/config中的信息设置特定的用户名和电子邮件地址|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3685688|您必须将模板目录的路径放入~/.gitconfig中|3685689|[init]
++++templatedir+=+~/.git/templates|code-block|syntax|javascript|3685690|然后，每个git+init或git+clone都将获得该钩子，并在下一个git+commit期间应用用户数据。如果你想将钩子应用到已经存在的repos上，那么只需要在repo中运行一个git+init来重新初始化它。|3685691|这是我想出来的钩子(它还需要改进--欢迎提出建议)。将其另存为|3685692|~/.git/templates/hooks/pre_commit|3685693|或|3685694|~/.git/templates/hooks/post-checkout|3685695|并确保它是可执行的：chmod+%2Bx+./post-checkout+%7C%7C+chmod+%2Bx+./pre_commit|3685696|#!/usr/bin/env+bash

#+--------+USER+CONFIG
#+Patterns+to+match+a+repo's+"remote.origin.url"+-+beginning+portion+of+the+hostname
git_remotes[0]="Github"
git_remotes[1]="Gitlab"

#+Adjust+names+and+e-mail+addresses
local_id_0[0]="my_name_0"
local_id_0[1]="my_email_0"

local_id_1[0]="my_name_1"
local_id_1[1]="my_email_1"

local_fallback_id[0]="${local_id_0[0]}"
local_fallback_id[1]="${local_id_0[1]}"


#+--------+FUNCTIONS
setIdentity()
{
++++local+current_id+local_id

++++current_id[0]="$(git+config+--get+--local+user.name)"
++++current_id[1]="$(git+config+--get+--local+user.email)"

++++local_id=("$@")

++++if+[[+"${current_id[0]}"+==+"${local_id[0]}"+&&
++++++++++"${current_id[1]}"+==+"${local_id[1]}"+]];+then
++++++++printf+"+Local+identity+is:\n"
++++++++printf+"»++User:+%25s\n»++Mail:+%25s\n\n"+"${current_id[@]}"
++++else
++++++++printf+"»++User:+%25s\n»++Mail:+%25s\n\n"+"${local_id[@]}"
++++++++git+config+--local+user.name+"${local_id[0]}"
++++++++git+config+--local+user.email+"${local_id[1]}"
++++fi

++++return+0
}

#+--------+IMPLEMENTATION
current_remote_url="$(git+config+--get+--local+remote.origin.url)"

if+[[+"$current_remote_url"+]];+then

++++for+service+in+"${git_remotes[@]}";+do

++++++++#+Disable+case+sensitivity+for+regex+matching
++++++++shopt+-s+nocasematch

++++++++if+[[+"$current_remote_url"+=~+$service+]];+then
++++++++++++case+"$service"+in

++++++++++++++++"${git_remotes[0]}"+)
++++++++++++++++++++printf+"\n»»+An+Intermission\n»++%25s+repository+found."+"${git_remotes[0]}"
++++++++++++++++++++setIdentity+"${local_id_0[@]}"
++++++++++++++++++++exit+0
++++++++++++++++++++;;

++++++++++++++++"${git_remotes[1]}"+)
++++++++++++++++++++printf+"\n»»+An+Intermission\n»++%25s+repository+found."+"${git_remotes[1]}"
++++++++++++++++++++setIdentity+"${local_id_1[@]}"
++++++++++++++++++++exit+0
++++++++++++++++++++;;

++++++++++++++++*+)
++++++++++++++++++++printf+"\n»++pre-commit+hook:+unknown+error\n»+Quitting.\n"
++++++++++++++++++++exit+1
++++++++++++++++++++;;

++++++++++++esac
++++++++fi
++++done
else
++++printf+"\n»»+An+Intermission\n»++No+remote+repository+set.+Using+local+fallback+identity:\n"
++++printf+"»++User:+%25s\n»++Mail:+%25s\n\n"+"${local_fallback_id[@]}"

++++#+Get+the+user's+attention+for+a+second
++++sleep+1

++++git+config+--local+user.name+"${local_fallback_id[0]}"
++++git+config+--local+user.email+"${local_fallback_id[1]}"
fi

exit+0|3685697|3685698|编辑：|3685699|所以我用Python将钩子重写为钩子和命令。此外，也可以将脚本作为Git命令(git+passport)调用。此外，还可以在配置文件(~/.gitpassport)中定义任意数量的ID，这些ID可以在提示符下选择。您可以在github.com：git-passport+-+A+Git+command+and+hook+written+in+Python+to+manage+multiple+Git+accounts+/+user+identities上找到该项目。|3685700|entityMap|0|LINK|mutability|MUTABLE|url|http://orrsella.com/2013/08/10/git-using-different-user-emails-for-different-repositories/|1|https://github.com/frace/git-passport^0|1B|M|2A|D|2|L|0|0|D|C|0|0|5|8|E|9|10|A|2K|8|0|0|0|0|0|A|1D|0|0|0|0|13|C|1V|E|3E|2X|1|0^^$0|@$1|2|3|4|5|6|7|1F|8|@$9|1G|A|1H|B|C]|$9|1I|A|1J|B|C]]|D|@$9|1K|A|1L|1|1M]]|E|$]]|$1|F|3|G|5|6|7|1N|8|@$9|1O|A|1P|B|C]]|D|@]|E|$]]|$1|H|3|I|5|J|7|1Q|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|1R|8|@$9|1S|A|1T|B|C]|$9|1U|A|1V|B|C]|$9|1W|A|1X|B|C]|$9|1Y|A|1Z|B|C]]|D|@]|E|$]]|$1|O|3|P|5|6|7|20|8|@]|D|@]|E|$]]|$1|Q|3|R|5|J|7|21|8|@]|D|@]|E|$K|L]]|$1|S|3|T|5|6|7|22|8|@]|D|@]|E|$]]|$1|U|3|V|5|J|7|23|8|@]|D|@]|E|$K|L]]|$1|W|3|X|5|6|7|24|8|@$9|25|A|26|B|C]]|D|@]|E|$]]|$1|Y|3|Z|5|J|7|27|8|@]|D|@]|E|$K|L]]|$1|10|3|-4|5|6|7|28|8|@]|D|@]|E|$]]|$1|11|3|12|5|6|7|29|8|@]|D|@]|E|$]]|$1|13|3|14|5|6|7|2A|8|@$9|2B|A|2C|B|C]|$9|2D|A|2E|B|C]]|D|@$9|2F|A|2G|1|2H]]|E|$]]|$1|15|3|-4|5|6|7|2I|8|@]|D|@]|E|$]]]|16|$17|$5|18|19|1A|E|$1B|1C]]|1D|$5|18|19|1A|E|$1B|1E]]]]

After getting some inspiration from <a href="http://orrsella.com/2013/08/10/git-using-different-user-emails-for-different-repositories/" rel="noreferrer">Orr Sella's blog post</a> I wrote a pre-commit hook (resides in <code>~/.git/templates/hooks</code>) which would set specific usernames and e-mail addresses based on the information inside a local repositorie's <code>./.git/config</code>:

You have to place the path to the template directory into your <code>~/.gitconfig</code>:

<pre><code>[init]
 templatedir = ~/.git/templates
</code></pre>

Then each <code>git init</code> or <code>git clone</code> will pick up that hook and will apply the user data during the next <code>git commit</code>. If you want to apply the hook to already exisiting repos then just run a <code>git init</code> inside the repo in order to reinitialize it.

Here is the hook I came up with (it still needs some polishing - suggestions are welcome).
Save it either as 

<pre><code>~/.git/templates/hooks/pre_commit
</code></pre>

or

<pre><code>~/.git/templates/hooks/post-checkout
</code></pre>

and make sure it is executable: <code>chmod +x ./post-checkout || chmod +x ./pre_commit</code>

<pre><code>#!/usr/bin/env bash

# -------- USER CONFIG
# Patterns to match a repo's "remote.origin.url" - beginning portion of the hostname
git_remotes[0]="Github"
git_remotes[1]="Gitlab"

# Adjust names and e-mail addresses
local_id_0[0]="my_name_0"
local_id_0[1]="my_email_0"

local_id_1[0]="my_name_1"
local_id_1[1]="my_email_1"

local_fallback_id[0]="${local_id_0[0]}"
local_fallback_id[1]="${local_id_0[1]}"


# -------- FUNCTIONS
setIdentity()
{
 local current_id local_id

 current_id[0]="$(git config --get --local user.name)"
 current_id[1]="$(git config --get --local user.email)"

 local_id=("$@")

 if [[ "${current_id[0]}" == "${local_id[0]}" &amp;&amp;
 "${current_id[1]}" == "${local_id[1]}" ]]; then
 printf " Local identity is:\n"
 printf "» User: %s\n» Mail: %s\n\n" "${current_id[@]}"
 else
 printf "» User: %s\n» Mail: %s\n\n" "${local_id[@]}"
 git config --local user.name "${local_id[0]}"
 git config --local user.email "${local_id[1]}"
 fi

 return 0
}

# -------- IMPLEMENTATION
current_remote_url="$(git config --get --local remote.origin.url)"

if [[ "$current_remote_url" ]]; then

 for service in "${git_remotes[@]}"; do

 # Disable case sensitivity for regex matching
 shopt -s nocasematch

 if [[ "$current_remote_url" =~ $service ]]; then
 case "$service" in

 "${git_remotes[0]}" )
 printf "\n»» An Intermission\n» %s repository found." "${git_remotes[0]}"
 setIdentity "${local_id_0[@]}"
 exit 0
 ;;

 "${git_remotes[1]}" )
 printf "\n»» An Intermission\n» %s repository found." "${git_remotes[1]}"
 setIdentity "${local_id_1[@]}"
 exit 0
 ;;

 * )
 printf "\n» pre-commit hook: unknown error\n» Quitting.\n"
 exit 1
 ;;

 esac
 fi
 done
else
 printf "\n»» An Intermission\n» No remote repository set. Using local fallback identity:\n"
 printf "» User: %s\n» Mail: %s\n\n" "${local_fallback_id[@]}"

 # Get the user's attention for a second
 sleep 1

 git config --local user.name "${local_fallback_id[0]}"
 git config --local user.email "${local_fallback_id[1]}"
fi

exit 0
</code></pre>

<hr>

EDIT:

So I rewrote the hook as a hook and command in Python. Additionally it's possible to call the script as a Git command (<code>git passport</code>), too. Also it's possible to define an arbitrary number of IDs inside a configfile (<code>~/.gitpassport</code>) which are selectable on a prompt. You can find the project at github.com: <a href="https://github.com/frace/git-passport" rel="noreferrer">git-passport - A Git command and hook written in Python to manage multiple Git accounts / user identities</a>.

blocks|key|3686270|text|有了Git2.13中的conditional+includes，现在可以让多个用户/电子邮件在一台机器上共存，而只需要很少的工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3686271|user.gitconfig有我的个人姓名和邮箱。work-user.gitconfig有我的工作名称和邮箱。这两个文件都位于~路径。|style|CODE|3686272|因此，默认情况下，我的个人姓名/电子邮件地址适用。对于c:/work/目录，应用我的工作名称/电子邮件。对于c:/work/github/目录，应用我的个人姓名/电子邮件。这在应用最后一个设置时起作用。|3686273|#+~/.gitconfig
[include]
++++path+=+user.gitconfig
[includeIf+"gitdir/i:c:/work/"]
++++path+=+work-user.gitconfig
[includeIf+"gitdir/i:c:/work/github/"]
++++path+=+user.gitconfig|code-block|syntax|javascript|3686274|gitdir区分大小写，而gitdir/i不区分大小写。|3686275|"gitdir/i:github/"将对路径中包含github的任何目录应用条件包含。|3686276|entityMap|0|LINK|mutability|MUTABLE|url|https://git-scm.com/docs/git-config#_conditional_includes^0|B|K|0|0|0|E|P|J|1R|1|0|R|8|1I|F|0|0|0|6|D|8|0|0|I|P|6|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@$A|11|B|12|1|13]]|C|$]]|$1|D|3|E|5|6|7|14|8|@$A|15|B|16|F|G]|$A|17|B|18|F|G]|$A|19|B|1A|F|G]]|9|@]|C|$]]|$1|H|3|I|5|6|7|1B|8|@$A|1C|B|1D|F|G]|$A|1E|B|1F|F|G]]|9|@]|C|$]]|$1|J|3|K|5|L|7|1G|8|@]|9|@]|C|$M|N]]|$1|O|3|P|5|6|7|1H|8|@$A|1I|B|1J|F|G]|$A|1K|B|1L|F|G]]|9|@]|C|$]]|$1|Q|3|R|5|6|7|1M|8|@$A|1N|B|1O|F|G]|$A|1P|B|1Q|F|G]]|9|@]|C|$]]|$1|S|3|-4|5|6|7|1R|8|@]|9|@]|C|$]]]|T|$U|$5|V|W|X|C|$Y|Z]]]]

With <a href="https://git-scm.com/docs/git-config#_conditional_includes" rel="noreferrer">conditional includes</a> in Git 2.13, it is now possible to have multiple user/email coexist on one machine with little work.

<code>user.gitconfig</code> has my personal name and email. <code>work-user.gitconfig</code> has my work name and email. Both files are at <code>~</code> path.

So my personal name/email applies by default. For <code>c:/work/</code> dir, my work name/email is applied. For <code>c:/work/github/</code> dir, my personal name/email is applied. This works as the last setting gets applied.

<pre><code># ~/.gitconfig
[include]
 path = user.gitconfig
[includeIf "gitdir/i:c:/work/"]
 path = work-user.gitconfig
[includeIf "gitdir/i:c:/work/github/"]
 path = user.gitconfig
</code></pre>

<code>gitdir</code> is case-sensitive and <code>gitdir/i</code> is case-insensitive.

<code>"gitdir/i:github/"</code> would apply the conditional include for any directory with <code>github</code> in its path.

blocks|key|1361908|text|如果您不想拥有默认电子邮件地址(email+address+links+to+a+github+user)，您可以配置您希望被询问的电子邮件地址。如何做到这一点取决于你使用的git版本，如下所示。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1361909|(预期的)缺点是，您必须为每个存储库配置一次电子邮件地址(和您的姓名)。所以，你不能忘记做这件事。|1361910|版本低于2.7.0|1361911|[user]
++++name+=+Your+name
++++email+=+"(none)"|code-block|syntax|javascript|1361912|在您的全局配置~/.gitconfig中，正如Dan+Aloni在Orr+Sella's+blog+post中的评论所述。当尝试在存储库中执行第一次提交时，git会失败，并显示一条很好的消息：|style|CODE|1361913|***+Please+tell+me+who+you+are.

Run

++git+config+--global+user.email+"you@example.com"
++git+config+--global+user.name+"Your+Name"

to+set+your+account's+default+identity.
Omit+--global+to+set+the+identity+only+in+this+repository.

fatal:+unable+to+auto-detect+email+address+(got+'(none)')|1361914|当电子邮件地址在本地设置时，该名称将从全局配置中获取(消息不完全准确)。|1361915|2.7.0≤版本低于2.8.0|1361916|低于2.7.0的版本中的行为不是预期的，并已在2.7.0中修复。您仍然可以使用Orr+Sella's+blog+post中描述的预提交钩子。此解决方案也适用于其他版本，但其他解决方案不适用于此版本。|1361917|版本≥2.8.0|1361918|Dan+Aloni+added提供了一个实现该行为的选项(参见release+notes)。将其与以下内容一起使用：|1361919|[user]
++++useConfigOnly+=+true|1361920|要使其正常工作，您不能在全局配置中提供名称或电子邮件地址。然后，在第一次提交时，您会收到一条错误消息|1361921|fatal:+user.useConfigOnly+set+but+no+name+given|1361922|因此，该消息不是很有指导意义，但是由于您显式地设置了该选项，因此您应该知道要做什么。与2.7.0以下版本的解决方案相比，您始终需要手动设置姓名和邮箱。|1361923|entityMap|0|LINK|mutability|MUTABLE|url|https://help.github.com/articles/setting-your-email-in-git/|1|https://orrsella.com/2013/08/10/git-using-different-user-emails-for-different-repositories/|2|3|http://git.661346.n2.nabble.com/PATCH-v9-ident-add-user-useConfigOnly-boolean-for-when-ident-shouldn-t-be-guessed-tp7647404.html|4|https://raw.githubusercontent.com/git/git/master/Documentation/RelNotes/2.8.0.txt^0|G|10|0|0|0|0|0|7|C|X|L|1|0|0|0|0|13|L|2|0|0|0|F|3|V|D|4|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1P|8|@]|9|@$A|1Q|B|1R|1|1S]]|C|$]]|$1|D|3|E|5|6|7|1T|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|1U|8|@]|9|@]|C|$]]|$1|H|3|I|5|J|7|1V|8|@]|9|@]|C|$K|L]]|$1|M|3|N|5|6|7|1W|8|@$A|1X|B|1Y|O|P]]|9|@$A|1Z|B|20|1|21]]|C|$]]|$1|Q|3|R|5|J|7|22|8|@]|9|@]|C|$K|L]]|$1|S|3|T|5|6|7|23|8|@]|9|@]|C|$]]|$1|U|3|V|5|6|7|24|8|@]|9|@]|C|$]]|$1|W|3|X|5|6|7|25|8|@]|9|@$A|26|B|27|1|28]]|C|$]]|$1|Y|3|Z|5|6|7|29|8|@]|9|@]|C|$]]|$1|10|3|11|5|6|7|2A|8|@]|9|@$A|2B|B|2C|1|2D]|$A|2E|B|2F|1|2G]]|C|$]]|$1|12|3|13|5|J|7|2H|8|@]|9|@]|C|$K|L]]|$1|14|3|15|5|6|7|2I|8|@]|9|@]|C|$]]|$1|16|3|17|5|J|7|2J|8|@]|9|@]|C|$K|L]]|$1|18|3|19|5|6|7|2K|8|@]|9|@]|C|$]]|$1|1A|3|-4|5|6|7|2L|8|@]|9|@]|C|$]]]|1B|$1C|$5|1D|1E|1F|C|$1G|1H]]|1I|$5|1D|1E|1F|C|$1G|1J]]|1K|$5|1D|1E|1F|C|$1G|1J]]|1L|$5|1D|1E|1F|C|$1G|1M]]|1N|$5|1D|1E|1F|C|$1G|1O]]]]

If you do not want to have a default email address (<a href="https://help.github.com/articles/setting-your-email-in-git/">email address links to a github user</a>), you can configure that you want to be asked. How you can do that depends on the version of git you use, see below.

The (intended) drawback is that you have to configure your email address (and your name) once for every repository. So, you cannot forget to do it.

<h2>Version &lt; 2.7.0</h2>

<pre><code>[user]
 name = Your name
 email = "(none)"
</code></pre>

in your global configuration <code>~/.gitconfig</code> as stated in a comment by Dan Aloni in <a href="https://orrsella.com/2013/08/10/git-using-different-user-emails-for-different-repositories/">Orr Sella's blog post</a>. When trying to do the first commit in a repository, git fails with the nice message:

<pre><code>*** Please tell me who you are.

Run

 git config --global user.email "you@example.com"
 git config --global user.name "Your Name"

to set your account's default identity.
Omit --global to set the identity only in this repository.

fatal: unable to auto-detect email address (got '(none)')
</code></pre>

The name is taken from the global config when the email address is set locally (the message is not perfectly accurate).

<h2>2.7.0 ≤ Version &lt; 2.8.0</h2>

The behaviour in versions &lt; 2.7.0 was not intended and fixed with 2.7.0. You can still use a pre-commit hook as described in <a href="https://orrsella.com/2013/08/10/git-using-different-user-emails-for-different-repositories/">Orr Sella's blog post</a>. This solution works also for other versions, but the other solutions not for this version.

<h2>Version ≥ 2.8.0</h2>

<a href="http://git.661346.n2.nabble.com/PATCH-v9-ident-add-user-useConfigOnly-boolean-for-when-ident-shouldn-t-be-guessed-tp7647404.html">Dan Aloni added</a> an option to achieve that behaviour (see <a href="https://raw.githubusercontent.com/git/git/master/Documentation/RelNotes/2.8.0.txt">release notes</a>). Use it with:

<pre><code>[user]
 useConfigOnly = true
</code></pre>

To make it work you may not give a name or email address in the global config. Then, at the first commit, you get an error message

<pre><code>fatal: user.useConfigOnly set but no name given
</code></pre>

So the message is not very instructive, but since you set the option explicitly, you should know what to do. In contrast to the solution of versions &lt; 2.7.0, you always have to set both name and email manually.

blocks|key|2108759|text|让git与多个名称/电子邮件一起工作的另一个选择是为git设置别名，并使用-c标志覆盖全局配置和特定于存储库的配置。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2108760|例如，通过定义别名：|2108761|alias+git='/usr/bin/git+-c+user.name="Your+name"+-c+user.email="name@example.com"'|code-block|syntax|javascript|2108762|要查看它是否工作，只需输入git+config+user.email|2108763|$+git+config+user.email
name@example.com|2108764|您还可以在$PATH中放置一个自定义的git可执行文件，而不是别名。|2108765|#!/bin/sh
/usr/bin/git+-c+user.name="Your+name"+-c+user.email="name@example.com"+"$@"|2108766|与特定于存储库的.git/config相比，这些方法的一个优点是，当自定义git程序处于活动状态时，它适用于每个git存储库。这样，您可以轻松地在用户/名称之间切换，而无需修改任何(共享的)配置。|2108767|entityMap^0|1|3|Q|3|11|2|0|0|0|D|L|0|0|5|5|J|3|0|0|8|B|11|3|1K|3|0^^$0|@$1|2|3|4|5|6|7|Y|8|@$9|Z|A|10|B|C]|$9|11|A|12|B|C]|$9|13|A|14|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|15|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|16|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|17|8|@$9|18|A|19|B|C]]|D|@]|E|$]]|$1|O|3|P|5|J|7|1A|8|@]|D|@]|E|$K|L]]|$1|Q|3|R|5|6|7|1B|8|@$9|1C|A|1D|B|C]|$9|1E|A|1F|B|C]]|D|@]|E|$]]|$1|S|3|T|5|J|7|1G|8|@]|D|@]|E|$K|L]]|$1|U|3|V|5|6|7|1H|8|@$9|1I|A|1J|B|C]|$9|1K|A|1L|B|C]|$9|1M|A|1N|B|C]]|D|@]|E|$]]|$1|W|3|-4|5|6|7|1O|8|@]|D|@]|E|$]]]|X|$]]

Another option to get <code>git</code> to work with multiple names / emails is by aliasing <code>git</code> and using the <code>-c</code> flag to override the global and repository-specific config.

For example, by defining an alias:

<pre class="lang-sh prettyprint-override"><code>alias git='/usr/bin/git -c user.name="Your name" -c user.email="name@example.com"'
</code></pre>

To see whether it works, simply type <code>git config user.email</code>:

<pre class="lang-sh prettyprint-override"><code>$ git config user.email
name@example.com
</code></pre>

Instead of an alias, you could also put a custom <code>git</code> executable within your <code>$PATH</code>.

<pre class="lang-sh prettyprint-override"><code>#!/bin/sh
/usr/bin/git -c user.name="Your name" -c user.email="name@example.com" "$@"
</code></pre>

An advantage of these method over a repository-specific <code>.git/config</code> is that it applies to every <code>git</code> repository when the custom <code>git</code> program is active. In this way, you can easily switch between users/names without modifying any (shared) configuration.

blocks|key|3686163|text|git别名(和git配置中的节)来拯救！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3686164|添加别名(从命令行)：|3686165|git+config+--global+alias.identity+'!+git+config+user.name+"$(git+config+user.$1.name)";+git+config+user.email+"$(git+config+user.$1.email)";+:'|code-block|syntax|javascript|3686166|然后，设置，例如|3686167|git+config+--global+user.github.name+"your+github+username"
git+config+--global+user.github.email+your@github.email|3686168|在新的或克隆的存储库中，您可以运行以下命令：|3686169|git+identity+github|3686170|这个解决方案不是自动的，但是在你的全局~/.gitconfig中取消用户和电子邮件设置并将user.useConfigOnly设置为true会强制git提醒你在每个新的或克隆的存储库中手动设置它们。|offset|length|style|CODE|3686171|git+config+--global+--unset+user.name
git+config+--global+--unset+user.email
git+config+--global+user.useConfigOnly+true|3686172|entityMap^0|0|0|0|0|0|0|0|J|C|19|I|1U|4|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|12|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|13|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|14|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|15|8|@]|9|@]|A|$]]|$1|O|3|P|5|F|7|16|8|@]|9|@]|A|$G|H]]|$1|Q|3|R|5|6|7|17|8|@$S|18|T|19|U|V]|$S|1A|T|1B|U|V]|$S|1C|T|1D|U|V]]|9|@]|A|$]]|$1|W|3|X|5|F|7|1E|8|@]|9|@]|A|$G|H]]|$1|Y|3|-4|5|6|7|1F|8|@]|9|@]|A|$]]]|Z|$]]

git aliases (and sections in git configs) to the rescue!

add an alias (from command line):

<pre><code>git config --global alias.identity '! git config user.name "$(git config user.$1.name)"; git config user.email "$(git config user.$1.email)"; :'
</code></pre>

then, set, for example

<pre><code>git config --global user.github.name "your github username"
git config --global user.github.email your@github.email
</code></pre>

and in a new or cloned repo you can run this command:

<pre><code>git identity github
</code></pre>

This solution isn't automatic, but unsetting user and email in your global <code>~/.gitconfig</code> and setting <code>user.useConfigOnly</code> to <code>true</code> would force git to remind you to set them manually in each new or cloned repo.

<pre><code>git config --global --unset user.name
git config --global --unset user.email
git config --global user.useConfigOnly true
</code></pre>

blocks|key|3686069|text|这个答案的部分灵感来自@Saucier的帖子，但我正在寻找一种自动方式，基于遥控器，在每个回购的基础上设置user.name和user.email，这比他开发的git-passport包要轻一点。对于useConfigOnly设置，还要将h/t发送给@John。以下是我的解决方案：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3686070|.gitconfig更改：|3686071|[github]
++++name+=+<github+username>
++++email+=+<github+email>
[gitlab]
++++name+=+<gitlab+username>
++++email+=+<gitlab+email>
[init]
++++templatedir+=+~/.git-templates
[user]
++++useConfigOnly+=+true|code-block|syntax|javascript|3686072|应保存到以下路径的结帐后hook：~/.git-templates/hooks/post-checkout|3686073|#!/usr/bin/env+bash

#+make+regex+matching+below+case+insensitive
shopt+-s+nocasematch

#+values+in+the+services+array+should+have+a+corresponding+section+in
#+.gitconfig+where+the+'name'+and+'email'+for+that+service+are+specified
remote_url="$(+git+config+--get+--local+remote.origin.url+)"
services=(
++++'github'
++++'gitlab'
)

set_local_user_config()+{
++++local+service="${1}"
++++local+config="${2}"
++++local+service_config="$(+git+config+--get+${service}.${config}+)"
++++local+local_config="$(+git+config+--get+--local+user.${config}+)"

++++if+[[+"${local_config}"+!=+"${service_config}"+]];+then
++++++++git+config+--local+"user.${config}"+"${service_config}"
++++++++echo+"repo+'user.${config}'+has+been+set+to+'${service_config}'"
++++fi
}

#+if+remote_url+doesn't+contain+the+any+of+the+values+in+the+services
#+array+the+user+name+and+email+will+remain+unset+and+the
#+user.useConfigOnly+=+true+setting+in+.gitconfig+will+prompt+for+those
#+credentials+and+prevent+commits+until+they+are+defined
for+s+in+"${services[@]}";+do
++++if+[[+"${remote_url}"+=~+"${s}"+]];+then
++++++++set_local_user_config+"${s}"+'name'
++++++++set_local_user_config+"${s}"+'email'
++++++++break
++++fi
done|3686074|我为github和gitlab使用了不同的凭证，但上面代码中的那些引用可以用您使用的任何服务替换或增强。为了让后结账钩子在结账后自动为存储库本地设置用户名和电子邮件，请确保服务名称出现在远程url中，将其添加到post-checkout脚本中的服务数组中，并在.gitconfig中为其创建一个包含该服务的用户名和电子邮件的部分。|3686075|如果没有服务名称出现在远程url中，或者repo没有遥控器，则不会在本地设置用户名和电子邮件。在这些情况下，user.useConfigOnly设置将起作用，它将不允许您进行提交，直到在存储库级别设置用户名和电子邮件，并将提示用户配置该信息。|3686076|entityMap|0|LINK|mutability|MUTABLE|url|https://git-scm.com/book/gr/v2/Customizing-Git-Git-Hooks^0|1H|9|1R|A|0|0|A|0|0|H|10|C|4|0|0|0|2X|D|3M|A|0|1I|I|0^^$0|@$1|2|3|4|5|6|7|12|8|@$9|13|A|14|B|C]|$9|15|A|16|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|17|8|@$9|18|A|19|B|C]]|D|@]|E|$]]|$1|H|3|I|5|J|7|1A|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|1B|8|@$9|1C|A|1D|B|C]]|D|@$9|1E|A|1F|1|1G]]|E|$]]|$1|O|3|P|5|J|7|1H|8|@]|D|@]|E|$K|L]]|$1|Q|3|R|5|6|7|1I|8|@$9|1J|A|1K|B|C]|$9|1L|A|1M|B|C]]|D|@]|E|$]]|$1|S|3|T|5|6|7|1N|8|@$9|1O|A|1P|B|C]]|D|@]|E|$]]|$1|U|3|-4|5|6|7|1Q|8|@]|D|@]|E|$]]]|V|$W|$5|X|Y|Z|E|$10|11]]]]

This answer is partially inspired by the post by @Saucier, but I was looking for an automated way to set <code>user.name</code> and <code>user.email</code> on a per repo basis, based on the remote, that was a little more light weight than the git-passport package that he developed. Also h/t to @John for the useConfigOnly setting. Here is my solution:

<code>.gitconfig</code> changes:

<pre><code>[github]
 name = &lt;github username&gt;
 email = &lt;github email&gt;
[gitlab]
 name = &lt;gitlab username&gt;
 email = &lt;gitlab email&gt;
[init]
 templatedir = ~/.git-templates
[user]
 useConfigOnly = true
</code></pre>

post-checkout <a href="https://git-scm.com/book/gr/v2/Customizing-Git-Git-Hooks" rel="noreferrer">hook</a> which should be saved to the following path: <code>~/.git-templates/hooks/post-checkout</code>:

<pre class="lang-bash prettyprint-override"><code>#!/usr/bin/env bash

# make regex matching below case insensitive
shopt -s nocasematch

# values in the services array should have a corresponding section in
# .gitconfig where the 'name' and 'email' for that service are specified
remote_url="$( git config --get --local remote.origin.url )"
services=(
 'github'
 'gitlab'
)

set_local_user_config() {
 local service="${1}"
 local config="${2}"
 local service_config="$( git config --get ${service}.${config} )"
 local local_config="$( git config --get --local user.${config} )"

 if [[ "${local_config}" != "${service_config}" ]]; then
 git config --local "user.${config}" "${service_config}"
 echo "repo 'user.${config}' has been set to '${service_config}'"
 fi
}

# if remote_url doesn't contain the any of the values in the services
# array the user name and email will remain unset and the
# user.useConfigOnly = true setting in .gitconfig will prompt for those
# credentials and prevent commits until they are defined
for s in "${services[@]}"; do
 if [[ "${remote_url}" =~ "${s}" ]]; then
 set_local_user_config "${s}" 'name'
 set_local_user_config "${s}" 'email'
 break
 fi
done
</code></pre>

I use different credentials for github and gitlab, but those references in the code above could be replaced or augmented with any service that you use. In order to have the post-checkout hook automatically set the user name and email locally for a repo after a checkout make sure the service name appears in the remote url, add it to the services array in the <code>post-checkout</code> script and create a section for it in your <code>.gitconfig</code> that contains your user name and email for that service. 

If none of the service names appear in the remote url or the repo doesn't have a remote the user name and email will not be set locally. In these cases the <code>user.useConfigOnly</code> setting will be in play which will not allow you to make commits until the user name and email are set at the repo level, and will prompt the user to configure that information.

blocks|key|21130|text|在阅读了这里的许多答案后，下面是完整的步骤|type|unstyled|depth|inlineStyleRanges|entityRanges|data|21131|如何为不同的github账号设置多个SSH密钥设置|21132|您可能希望开始检查当前保存的密钥|21133|$+ssh-add+-l|code-block|syntax|javascript|21134|如果您之前决定删除所有缓存的键(optional，carefull+you+this)|offset|length|style|BOLD|21135|$+ssh-add+-D|21136|然后，您可以创建一个链接到您希望/需要使用的每个电子邮件/帐户的ssh+pub/priv密钥|21137|$+cd+~/.ssh
$+ssh-keygen+-t+rsa+-C+"work@company.com"+<--+save+it+as+"id_rsa_work"
$+ssh-keygen+-t+rsa+-C+"pers@email.com"+<--+save+it+as+"id_rsa_pers"|21138|执行此命令后，您将创建以下文件|21139|~/.ssh/id_rsa_work++++++
~/.ssh/id_rsa_work.pub

~/.ssh/id_rsa_pers
~/.ssh/id_rsa_pers.pub+|21140|确保身份验证代理正在运行|21141|$+eval+`ssh-agent+-s`|21142|添加生成的密钥，如下所示(从~/.ssh文件夹)|21143|$+ssh-add+id_rsa_work
$+ssh-add+id_rsa_pers|21144|现在您可以再次检查您保存的密钥|21145|$+ssh-add+-l|21146|现在，您需要将生成的公钥添加到github/bickbuket服务器访问密钥中|21147|将每个存储库克隆到不同的文件夹|21148|转到用户+work+将工作的文件夹并执行以下命令|21149|$+git+config+user.name+"Working+Hard"
$+git+config+user.email+"work@company.com"+|21150|为了了解它的作用，请检查".git/config“文件的内容|21151|转到用户pers将工作的文件夹，并执行以下命令|21152|$+git+config+user.name+"Personal+Account"
$+git+config+user.email+"pers@email.com"+|21153|21154|完成这一切后，您只需在这两个文件夹之间切换，即可提交您的个人代码和工作代码|21155|如果您使用的是Git+Bash，并且需要在Windows下生成ssh密钥，请执行以下步骤：|21156|https://support.automaticsync.com/hc/en-us/articles/202357115-Generating-an-SSH-Key-on-Windows|21157|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|0|G|Q|0|0|0|0|0|0|2|6|0|0|0|0|0|0|0|0|4|6|0|0|0|4|4|0|0|0|0|0|0|2M|0|0^^$0|@$1|2|3|4|5|6|7|24|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|25|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|26|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|27|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|28|8|@$M|29|N|2A|O|P]]|9|@]|A|$]]|$1|Q|3|R|5|H|7|2B|8|@]|9|@]|A|$I|J]]|$1|S|3|T|5|6|7|2C|8|@]|9|@]|A|$]]|$1|U|3|V|5|H|7|2D|8|@]|9|@]|A|$I|J]]|$1|W|3|X|5|6|7|2E|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|H|7|2F|8|@]|9|@]|A|$I|J]]|$1|10|3|11|5|6|7|2G|8|@$M|2H|N|2I|O|P]]|9|@]|A|$]]|$1|12|3|13|5|H|7|2J|8|@]|9|@]|A|$I|J]]|$1|14|3|15|5|6|7|2K|8|@]|9|@]|A|$]]|$1|16|3|17|5|H|7|2L|8|@]|9|@]|A|$I|J]]|$1|18|3|19|5|6|7|2M|8|@]|9|@]|A|$]]|$1|1A|3|1B|5|H|7|2N|8|@]|9|@]|A|$I|J]]|$1|1C|3|1D|5|6|7|2O|8|@]|9|@]|A|$]]|$1|1E|3|1F|5|6|7|2P|8|@]|9|@]|A|$]]|$1|1G|3|1H|5|6|7|2Q|8|@$M|2R|N|2S|O|P]]|9|@]|A|$]]|$1|1I|3|1J|5|H|7|2T|8|@]|9|@]|A|$I|J]]|$1|1K|3|1L|5|6|7|2U|8|@]|9|@]|A|$]]|$1|1M|3|1N|5|6|7|2V|8|@$M|2W|N|2X|O|P]]|9|@]|A|$]]|$1|1O|3|1P|5|H|7|2Y|8|@]|9|@]|A|$I|J]]|$1|1Q|3|1L|5|6|7|2Z|8|@]|9|@]|A|$]]|$1|1R|3|1S|5|6|7|30|8|@]|9|@]|A|$]]|$1|1T|3|1U|5|6|7|31|8|@]|9|@]|A|$]]|$1|1V|3|1W|5|6|7|32|8|@]|9|@$M|33|N|34|1|35]]|A|$]]|$1|1X|3|-4|5|6|7|36|8|@]|9|@]|A|$]]]|1Y|$1Z|$5|20|21|22|A|$23|1W]]]]

Here are the complete steps after reading many answers here

How to set up Multiple SSH Keys settings for different github account

You might want to start checking your currently saved keys

<pre><code>$ ssh-add -l
</code></pre>

If you decide to delete all cached keys before (optional, carefull about this)

<pre><code>$ ssh-add -D
</code></pre>

Then you can create a ssh pub/priv key linked to each email/account that you wish/need to use

<pre><code>$ cd ~/.ssh
$ ssh-keygen -t rsa -C "work@company.com" &lt;-- save it as "id_rsa_work"
$ ssh-keygen -t rsa -C "pers@email.com" &lt;-- save it as "id_rsa_pers"
</code></pre>

After performing this commands you will have the following files created

<pre><code>~/.ssh/id_rsa_work 
~/.ssh/id_rsa_work.pub

~/.ssh/id_rsa_pers
~/.ssh/id_rsa_pers.pub 
</code></pre>

Make sure authentication agent is running 

<pre><code>$ eval `ssh-agent -s`
</code></pre>

Add the generated keys as following (from the ~/.ssh folder)

<pre><code>$ ssh-add id_rsa_work
$ ssh-add id_rsa_pers
</code></pre>

Now you can check your saved keys again

<pre><code>$ ssh-add -l
</code></pre>

Now you need to add the generated public keys to your github/bickbuket server Acces Keys

Clone each of the repos to different folders 

Go to the folder where the user work will work and execute this

<pre><code>$ git config user.name "Working Hard"
$ git config user.email "work@company.com" 
</code></pre>

Just to see what this does check the contents of the ".git/config" 

Go to the folder where the user pers will work and execute this 

<pre><code>$ git config user.name "Personal Account"
$ git config user.email "pers@email.com" 
</code></pre>

Just to see what this does check the contents of the ".git/config" 

After all this you will be able to commit your personal and work code by just switching between those two folders

In case you are using Git Bash and need to generate ssh keys under Windows follow this steps:

<a href="https://support.automaticsync.com/hc/en-us/articles/202357115-Generating-an-SSH-Key-on-Windows" rel="nofollow noreferrer">https://support.automaticsync.com/hc/en-us/articles/202357115-Generating-an-SSH-Key-on-Windows</a>

blocks|key|2108856|text|有一个简单的解决方案，似乎可以很好地避免错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2108857|只需从您的~/.gitconfig中删除[user]部分，这将阻止您在没有为每个存储库设置user.name的情况下进行任何提交。|offset|length|style|CODE|2108858|在~/.bashrc中，为用户和电子邮件添加一些简单的别名：|2108859|alias+ggmail='git+config+user.name+"My+Name";git+config+user.email+me@gmail.com'
alias+gwork='git+config+user.name+"My+Name";git+config+user.email+me@work.job'|code-block|syntax|javascript|2108860|entityMap^0|0|5|C|K|6|19|9|0|1|9|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@$D|S|E|T|F|G]|$D|U|E|V|F|G]|$D|W|E|X|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|Y|8|@$D|Z|E|10|F|G]]|9|@]|A|$]]|$1|J|3|K|5|L|7|11|8|@]|9|@]|A|$M|N]]|$1|O|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|P|$]]

There is a simple solution that seems to work well for avoiding mistakes.

Simply remove the <code>[user]</code> section from your <code>~/.gitconfig</code>, which will prevent you from making any commits without setting <code>user.name</code> for each repository.

In your <code>~/.bashrc</code>, add some simple aliases for the user and email:

<pre><code>alias ggmail='git config user.name "My Name";git config user.email me@gmail.com'
alias gwork='git config user.name "My Name";git config user.email me@work.job'
</code></pre>

blocks|key|3686652|text|在阅读完所有答案后，这是我提出的解决方案：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3686653|场景：|offset|length|style|BOLD|3686654|3686655|本地操作系统:+Linux+(Bash)|unordered-list-item|3686656|+GitHub+(work/personal)|3686657|ssh+access上的两个帐户使用不同的密钥|3686658|我的工作帐户将是“主”帐户(因此它不需要自定义的bash|3686659|3686660|Configuration:|3686661|3686662|设置了一个“假”主机，让我可以选择合适的密钥对。|ordered-list-item|3686663|3686664|在~/.ssh/config：#+Personal+GitHub+account+Host+github-personal+HostName+github.com+User+git+IdentityFile+~/.ssh/id_rsa_personal+IdentitiesOnly+yes|CODE|3686665|3686666|“告诉”git它应该在给定的目录子树中使用自定义配置：|3686667|3686668|在~/.gitconfig：#+My+personal+projects+includeIf+"gitdir/i:~/REPOS/PERSONAL/“path+=gitdir|3686669|最后，我在~/REPOS/PERSONAL/personal.gitconfig上的配置：#+gitconfig++personal+projects+user+email+=+personalemail@example.com+url+"git@github-personal“insteadOf+=gitconfig|3686670|一旦以上三个准备就绪，我就可以像这样克隆一个个人回购：|3686671|user@host:~/REPOS/PERSONAL$+git+clone+git@github.com:jmnavarrol/python-multigit.git
Cloning+in+'python-multigit'...
(...)
user@host:~/REPOS/PERSONAL$+cd+python-multigit+&&+git+remote+-v
origin++git@github-personal:jmnavarrol/python-multigit.git+(fetch)
origin++git@github-personal:jmnavarrol/python-multigit.git+(push)
user@host:~/REPOS/PERSONAL/python-multigit$|code-block|syntax|javascript|3686672|在~/REPOS/PERSONAL/personal.gitconfig上添加了url重写...|3686673|[url+"git@github-personal"]
++insteadOf+=+git@github.com|3686674|...is允许我只通过脚本、subrepos中的“标准”URL来引用repo+(例如，python-multigit+itself+-yes的情况，一些自我推广的尝试)，而不会冒着使用“错误的”URL的风险，因此，错误的身份验证。|3686675|我的两点意见。|3686676|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/jmnavarrol/python-multigit^0|0|0|3|0|0|0|0|0|0|0|0|E|0|0|0|0|1|D|0|0|0|0|1|C|0|5|Z|0|0|0|1|Z|0|0|17|M|0|0|0^^$0|@$1|2|3|4|5|6|7|1X|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1Y|8|@$D|1Z|E|20|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|21|8|@]|9|@]|A|$]]|$1|I|3|J|5|K|7|22|8|@]|9|@]|A|$]]|$1|L|3|M|5|K|7|23|8|@]|9|@]|A|$]]|$1|N|3|O|5|K|7|24|8|@]|9|@]|A|$]]|$1|P|3|Q|5|K|7|25|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|26|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|27|8|@$D|28|E|29|F|G]]|9|@]|A|$]]|$1|U|3|-4|5|6|7|2A|8|@]|9|@]|A|$]]|$1|V|3|W|5|X|7|2B|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|2C|8|@]|9|@]|A|$]]|$1|Z|3|10|5|6|7|2D|8|@$D|2E|E|2F|F|11]]|9|@]|A|$]]|$1|12|3|-4|5|6|7|2G|8|@]|9|@]|A|$]]|$1|13|3|14|5|X|7|2H|8|@]|9|@]|A|$]]|$1|15|3|-4|5|6|7|2I|8|@]|9|@]|A|$]]|$1|16|3|17|5|6|7|2J|8|@$D|2K|E|2L|F|11]]|9|@]|A|$]]|$1|18|3|19|5|6|7|2M|8|@$D|2N|E|2O|F|11]]|9|@]|A|$]]|$1|1A|3|1B|5|6|7|2P|8|@]|9|@]|A|$]]|$1|1C|3|1D|5|1E|7|2Q|8|@]|9|@]|A|$1F|1G]]|$1|1H|3|1I|5|6|7|2R|8|@$D|2S|E|2T|F|11]]|9|@]|A|$]]|$1|1J|3|1K|5|1E|7|2U|8|@]|9|@]|A|$1F|1G]]|$1|1L|3|1M|5|6|7|2V|8|@]|9|@$D|2W|E|2X|1|2Y]]|A|$]]|$1|1N|3|1O|5|6|7|2Z|8|@]|9|@]|A|$]]|$1|1P|3|-4|5|6|7|30|8|@]|9|@]|A|$]]]|1Q|$1R|$5|1S|1T|1U|A|$1V|1W]]]]

After reading all the answers, that's the solution I came with:
Scenario:
<ul>
<li>Local OS: Linux (bash)</li>
<li>two accounts on GitHub (work/personal)</li>
<li>ssh access with different keys</li>
<li>my work account will be the &quot;main&quot; one (so it doesn't need custom configuration)</li>
</ul>
Configuration:
<ol>
<li>Set a &quot;fake&quot; host, which allows me to select the proper SSH keypair. 
At <code>~/.ssh/config</code>:
<pre class="lang-sh prettyprint-override"><code># Personal GitHub account
Host github-personal
 HostName github.com
 User git
 IdentityFile ~/.ssh/id_rsa_personal
 IdentitiesOnly yes
</code></pre>
</li>
<li>&quot;Tell&quot; git it should use a custom configuration within a given directory subtree: 
At <code>~/.gitconfig</code>:
<pre class="lang-sh prettyprint-override"><code># My personal projects
[includeIf &quot;gitdir/i:~/REPOS/PERSONAL/&quot;]
 path = ~/REPOS/PERSONAL/personal.gitconfig

</code></pre>
</li>
<li>Finally, my config at <code>~/REPOS/PERSONAL/personal.gitconfig</code>:
<pre class="lang-sh prettyprint-override"><code># gitconfig for personal projects
[user]
 email = personalemail@example.com

[url &quot;git@github-personal&quot;]
 insteadOf = git@github.com
</code></pre>
</li>
</ol>
Once the three above are in place, I can clone a personal repo like this:
<pre class="lang-sh prettyprint-override"><code>user@host:~/REPOS/PERSONAL$ git clone git@github.com:jmnavarrol/python-multigit.git
Cloning in 'python-multigit'...
(...)
user@host:~/REPOS/PERSONAL$ cd python-multigit &amp;&amp; git remote -v
origin git@github-personal:jmnavarrol/python-multigit.git (fetch)
origin git@github-personal:jmnavarrol/python-multigit.git (push)
user@host:~/REPOS/PERSONAL/python-multigit$
</code></pre>
The addition of the url rewriting at <code>~/REPOS/PERSONAL/personal.gitconfig</code>...
<pre class="lang-sh prettyprint-override"><code>[url &quot;git@github-personal&quot;]
 insteadOf = git@github.com
</code></pre>
...is what allows me referencing the repo just by its &quot;standard&quot; URL in scripts, subrepos (i.e. the case of <a href="https://github.com/jmnavarrol/python-multigit" rel="noreferrer">python-multigit itself</a> -yes, lame attempt at a bit of self-promotion) without risking using the &quot;wrong&quot; URLs, therefore, the wrong authentication.
My two cents.

blocks|key|1360453|text|Windows环境|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1360454|另外，如果您的系统中安装了Git+Extensions+-->+Settings+-->+Global+Settings，则可以从它进行修改。|CODE|1360455|gitextensions-latest-release|1360456|右键单击Windows环境中的文件夹/目录可访问这些设置。|1360457|📷|atomic|1360458|​|1360459|更新：如何在版本2.49中切换/维护多个设置|1360460|1360461|1360462|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/gitextensions/gitextensions/releases/latest|1|IMAGE|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/be77f3150b52310d2c7a8b124e4cdb0f.png|imageAlt|2|https://ask.qcloudimg.com/http-save/yehe-900000/1e7e4071eb370c5cd4ff2039c80e774e.png^0|0|9|0|D|1B|0|0|S|0|0|0|0|1|1|0|0|0|2|0|0|1|2|0|0^^$0|@$1|2|3|4|5|6|7|1B|8|@$9|1C|A|1D|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1E|8|@$9|1F|A|1G|B|H]]|D|@]|E|$]]|$1|I|3|J|5|6|7|1H|8|@]|D|@$9|1I|A|1J|1|1K]]|E|$]]|$1|K|3|L|5|6|7|1L|8|@]|D|@]|E|$]]|$1|M|3|N|5|O|7|1M|8|@]|D|@$9|1N|A|1O|1|1P]]|E|$]]|$1|P|3|Q|5|6|7|1Q|8|@]|D|@]|E|$]]|$1|R|3|S|5|6|7|1R|8|@$9|1S|A|1T|B|C]]|D|@]|E|$]]|$1|T|3|N|5|O|7|1U|8|@]|D|@$9|1V|A|1W|1|1X]]|E|$]]|$1|U|3|Q|5|6|7|1Y|8|@]|D|@]|E|$]]|$1|V|3|-4|5|6|7|1Z|8|@]|D|@]|E|$]]]|W|$X|$5|Y|Z|10|E|$11|12]]|13|$5|14|Z|15|E|$16|17|18|-4]]|19|$5|14|Z|15|E|$16|1A|18|-4]]]]

Windows Environment

Additional this can be modified from <code>Git Extensions --&gt; Settings --&gt; Global Settings</code>, if you have it installed in your systems.

<a href="https://github.com/gitextensions/gitextensions/releases/latest" rel="nofollow noreferrer">gitextensions-latest-release</a>

Right Click on a folder/directory in Windows Environment to access these settings.
<img src="https://i.stack.imgur.com/mdgMc.png" alt="enter image description here">

Update : How to switch/maintain multiple settings in Version 2.49
<a href="https://i.stack.imgur.com/SGyzn.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/SGyzn.png" alt="How to switch/maintain multiple settings in Version 2.49"></a>

blocks|key|20763|text|GIT_AUTHOR_EMAIL+.bashrc+%2B本地|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|CODE|entityRanges|data|20764|.bashrc_local：不要跟踪此文件，只将其放在您的工作计算机上：|20765|export+GIT_AUTHOR_EMAIL='me@work.com'
export+GIT_COMMITTER_EMAIL="$GIT_AUTHOR_EMAIL"|code-block|syntax|javascript|20766|.bashrc：跟踪此文件，使其在工作计算机和家庭计算机上都相同：|20767|F="$HOME/.bashrc_local"
if+[+-r+"$F"+];+then
++++.+"$F"
fi|20768|我正在使用https://github.com/technicalpickles/homesick来同步我的点文件。|20769|如果gitconfig可以接受环境变量：Shell+variable+expansion+in+git+config|20770|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/technicalpickles/homesick|1|https://stackoverflow.com/questions/11262010/shell-variable-expansion-in-git-config^0|0|G|H|7|0|G|H|7|0|0|D|0|0|0|7|0|0|5|18|0|0|K|12|1|0^^$0|@$1|2|3|4|5|6|7|15|8|@$9|16|A|17|B|C]|$9|18|A|19|B|C]|$9|1A|A|1B|B|D]|$9|1C|A|1D|B|D]]|E|@]|F|$]]|$1|G|3|H|5|6|7|1E|8|@$9|1F|A|1G|B|D]]|E|@]|F|$]]|$1|I|3|J|5|K|7|1H|8|@]|E|@]|F|$L|M]]|$1|N|3|O|5|6|7|1I|8|@$9|1J|A|1K|B|D]]|E|@]|F|$]]|$1|P|3|Q|5|K|7|1L|8|@]|E|@]|F|$L|M]]|$1|R|3|S|5|6|7|1M|8|@]|E|@$9|1N|A|1O|1|1P]]|F|$]]|$1|T|3|U|5|6|7|1Q|8|@]|E|@$9|1R|A|1S|1|1T]]|F|$]]|$1|V|3|-4|5|6|7|1U|8|@]|E|@]|F|$]]]|W|$X|$5|Y|Z|10|F|$11|12]]|13|$5|Y|Z|10|F|$11|14]]]]

<code>GIT_AUTHOR_EMAIL</code> + local <code>.bashrc</code>

<code>.bashrc_local</code>: don't track this file, put it only on your work computer:

<pre><code>export GIT_AUTHOR_EMAIL='me@work.com'
export GIT_COMMITTER_EMAIL="$GIT_AUTHOR_EMAIL"
</code></pre>

<code>.bashrc</code>: track this file, make it the same on both work and home computers:

<pre><code>F="$HOME/.bashrc_local"
if [ -r "$F" ]; then
 . "$F"
fi
</code></pre>

I'm using <a href="https://github.com/technicalpickles/homesick" rel="nofollow noreferrer">https://github.com/technicalpickles/homesick</a> to sync my dotfiles.

If only gitconfig would accept environment variables: <a href="https://stackoverflow.com/questions/11262010/shell-variable-expansion-in-git-config">Shell variable expansion in git config</a>

blocks|key|3686113|text|也许这是一个简单的技巧，但它是有用的。只需生成2个ssh密钥，如下所示。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3686114|Generating+public/private+rsa+key+pair.
Enter+file+in+which+to+save+the+key+(/Users/GowthamSai/.ssh/id_rsa):+work
Enter+passphrase+(empty+for+no+passphrase):
Enter+same+passphrase+again:
Your+identification+has+been+saved+in+damsn.
Your+public+key+has+been+saved+in+damsn.pub.
The+key+fingerprint+is:
SHA256:CrsKDJWVVek5GTCqmq8/8RnwvAo1G6UOmQFbzddcoAY+GowthamSai@Gowtham-MacBook-Air.local
The+key's+randomart+image+is:
%2B---[RSA+4096]----%2B
%7C.+.oEo%2B=o%2B.++++++%7C
%7C.o+o%2Bo.o=++++++++%7C
%7Co+o+o.o.+%2B+++++++%7C
%7C+=.%2B+.++=++++++++%7C
%7C=+*%2B.+++S.+++++++%7C
%7Co*.%2B%2Bo+.+++++++++%7C
%7C=.oo.%2B.++++++++++%7C
%7C+%2B.+%2B.+++++++++++%7C
%7C.o=%2B.++++++++++++%7C
%2B----[SHA256]-----%2B|code-block|syntax|javascript|3686115|以同样的方式为个人创建多一个。所以，你有两个ssh密钥，一个是work，一个是company。将work.pub、work、personal.pub、personal复制到~/.ssh/目录。|offset|length|style|BOLD|3686116|然后创建一个包含以下代码行的shell脚本，并将其命名为crev.sh+(Company+Reverse)，其中包含以下内容。|3686117|cp+~/.ssh/work+~/.ssh/id_rsa
cp+~/.ssh/work.pub+~/.ssh/id_rsa.pub|3686118|同样，使用以下内容再创建一个名为prev.sh+(Personal+Reverse)的应用程序。|3686119|cp+~/.ssh/personal+~/.ssh/id_rsa
cp+~/.ssh/personal.pub+~/.ssh/id_rsa.pub|3686120|在~/.bashrc中为这些脚本添加别名，如下所示|3686121|alias+crev="sh+~/.ssh/crev.sh"
alias+prev="sh+~/.ssh/prev.sh"
source+~/.bashrc|3686122|当你想使用公司的时候，只需要使用crev，如果你想使用个人的，就使用prev+:-p。|3686123|将这些ssh密钥添加到您的GitHub帐户。确保之前没有生成id_rsa，因为这些脚本将覆盖id_rsa。如果您已经生成了id_rsa，请将其用于其中一个帐户。将它们复制为个人密钥，并跳过生成个人密钥的过程。|3686124|entityMap^0|0|0|2E|7|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|14|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|15|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|16|8|@$I|17|J|18|K|L]]|9|@]|A|$]]|$1|M|3|N|5|6|7|19|8|@]|9|@]|A|$]]|$1|O|3|P|5|D|7|1A|8|@]|9|@]|A|$E|F]]|$1|Q|3|R|5|6|7|1B|8|@]|9|@]|A|$]]|$1|S|3|T|5|D|7|1C|8|@]|9|@]|A|$E|F]]|$1|U|3|V|5|6|7|1D|8|@]|9|@]|A|$]]|$1|W|3|X|5|D|7|1E|8|@]|9|@]|A|$E|F]]|$1|Y|3|Z|5|6|7|1F|8|@]|9|@]|A|$]]|$1|10|3|11|5|6|7|1G|8|@]|9|@]|A|$]]|$1|12|3|-4|5|6|7|1H|8|@]|9|@]|A|$]]]|13|$]]

Maybe it is a simple hack, but it is useful. Just generate 2 ssh keys like below.

<pre><code>Generating public/private rsa key pair.
Enter file in which to save the key (/Users/GowthamSai/.ssh/id_rsa): work
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in damsn.
Your public key has been saved in damsn.pub.
The key fingerprint is:
SHA256:CrsKDJWVVek5GTCqmq8/8RnwvAo1G6UOmQFbzddcoAY GowthamSai@Gowtham-MacBook-Air.local
The key's randomart image is:
+---[RSA 4096]----+
|. .oEo+=o+. |
|.o o+o.o= |
|o o o.o. + |
| =.+ . = |
|= *+. S. |
|o*.++o . |
|=.oo.+. |
| +. +. |
|.o=+. |
+----[SHA256]-----+
</code></pre>

Same way create one more for personal. So, you have 2 ssh keys, work and company. Copy work.pub, work, personal.pub, personal to ~/.ssh/ Directory. 

Then create a shell script with the following lines and name it as crev.sh (Company Reverse) with the following content. 

<pre><code>cp ~/.ssh/work ~/.ssh/id_rsa
cp ~/.ssh/work.pub ~/.ssh/id_rsa.pub
</code></pre>

Same way, create one more called prev.sh (Personal Reverse) with the following content. 

<pre><code>cp ~/.ssh/personal ~/.ssh/id_rsa
cp ~/.ssh/personal.pub ~/.ssh/id_rsa.pub
</code></pre>

in ~/.bashrc add aliases for those scripts like below 

<pre><code>alias crev="sh ~/.ssh/crev.sh"
alias prev="sh ~/.ssh/prev.sh"
source ~/.bashrc
</code></pre>

Whenever you wanna use company, just do crev, and if you wanna use personal do prev :-p. 

Add those ssh keys to your GitHub accounts. Make sure, you don't have id_rsa generated previously, because those scripts will overwrite id_rsa. If you have already generated id_rsa, use that for one of the accounts. Copy them as personal and skip the generation of personal keys.

blocks|key|3686343|text|我做了一个bash函数来处理这个问题。Here+is+the+Github+repo。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3686344|对于记录：|3686345|#+Look+for+closest+.gitconfig+file+in+parent+directories
#+This+file+will+be+used+as+main+.gitconfig+file.
function+__recursive_gitconfig_git+{
++++gitconfig_file=$(__recursive_gitconfig_closest)
++++if+[+"$gitconfig_file"+!=+''+];+then
++++++++home="$(dirname+$gitconfig_file)/"
++++++++HOME=$home+/usr/bin/git+"$@"
++++else
++++++++/usr/bin/git+"$@"
++++fi
}

#+Look+for+closest+.gitconfig+file+in+parents+directories
function+__recursive_gitconfig_closest+{
++++slashes=${PWD//[%5E\/]/}
++++directory="$PWD"
++++for+((+n=${#slashes};+n>0;+--n+))
++++do
++++++++test+-e+"$directory/.gitconfig"+&&+echo+"$directory/.gitconfig"+&&+return+
++++++++directory="$directory/.."
++++done
}


alias+git='__recursive_gitconfig_git'|code-block|syntax|javascript|3686346|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/arount/recursive-gitconfig^0|J|N|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@$A|T|B|U|1|V]]|C|$]]|$1|D|3|E|5|6|7|W|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|X|8|@]|9|@]|C|$I|J]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|C|$]]]|L|$M|$5|N|O|P|C|$Q|R]]]]

I made a bash function that handle that. <a href="https://github.com/arount/recursive-gitconfig" rel="nofollow noreferrer">Here is the Github repo</a>.

For record:

<pre><code># Look for closest .gitconfig file in parent directories
# This file will be used as main .gitconfig file.
function __recursive_gitconfig_git {
 gitconfig_file=$(__recursive_gitconfig_closest)
 if [ "$gitconfig_file" != '' ]; then
 home="$(dirname $gitconfig_file)/"
 HOME=$home /usr/bin/git "$@"
 else
 /usr/bin/git "$@"
 fi
}

# Look for closest .gitconfig file in parents directories
function __recursive_gitconfig_closest {
 slashes=${PWD//[^\/]/}
 directory="$PWD"
 for (( n=${#slashes}; n&gt;0; --n ))
 do
 test -e "$directory/.gitconfig" &amp;&amp; echo "$directory/.gitconfig" &amp;&amp; return 
 directory="$directory/.."
 done
}


alias git='__recursive_gitconfig_git'
</code></pre>

blocks|key|2109090|text|尽管大多数问题都在某种程度上回答了这个问题，但我只是自己经历了这个问题，甚至不用谷歌搜索，我就能够找到最快、最简单的解决方案。下面是一些简单的步骤：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2109091|2109092|从您的其他存储库复制现有文件，并将其粘贴到新添加的存储库|unordered-list-item|2109093|更改.gitconfig文件中的值，例如名称、电子邮件和用户名[user]+++++name+=+John+++++email+=+john@email.net+++++username+=+john133+H29H110将文件名添加到D11列表中，以确保不将D12文件提交到您的工作存储库H213F214|offset|length|style|CODE|2109094|2109095|entityMap^0|0|0|0|2|A|V|20|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|P|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|Q|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|R|8|@$H|S|I|T|J|K]|$H|U|I|V|J|K]]|9|@]|A|$]]|$1|L|3|-4|5|6|7|W|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|N|$]]

Although most questions sort of answered the OP, I just had to go through this myself and without even googling I was able to find the quickest and simplest solution. Here's simple steps:

<ul>
<li>copy existing <code>.gitconfg</code> from your other repo</li>
<li>paste into your newly added repo </li>
<li>change values in <code>.gitconfig</code> file, such as name, email and username
<code>
[user]
 name = John
 email = john@email.net
 username = john133
</code></li>
<li>add filename to <code>.gitignore</code> list, to make sure you don't commit <code>.gitconfig</code> file to your work repo</li>
</ul>

blocks|key|1362304|text|您还可以在想要以不同用户身份提交的存储库中执行提交时使用git+commit+--author+"Your+Name+<your@email.com>"。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1362305|entityMap^0|S|1C|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

You can also use <code>git commit --author "Your Name &lt;your@email.com&gt;"</code> at the moment of doing a commit in a repo where you want to commit as a different user.

blocks|key|2104895|text|类似于Rob+W's+answer，但允许使用不同的ssh密钥，并且适用于较旧的git版本(没有core.sshCommand配置)。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2104896|我创建了具有可执行权限的文件~/bin/git_poweruser，其路径为：|style|CODE|2104897|#!/bin/bash

TMPDIR=$(mktemp+-d)
trap+'rm+-rf+"$TMPDIR"'+EXIT

cat+>+$TMPDIR/ssh+<<+'EOF'
#!/bin/bash
ssh+-i+$HOME/.ssh/poweruserprivatekey+$@
EOF

chmod+%2Bx+$TMPDIR/ssh
export+GIT_SSH=$TMPDIR/ssh

git+-c+user.name="Power+User+name"+-c+user.email="power@user.email"+$@|code-block|syntax|javascript|2104898|当我想以“高级用户”的身份提交或推送某些东西时，我会使用git_poweruser而不是git。它应该可以在任何目录下工作，并且不需要在.gitconfig或.ssh/config中更改，至少在我的目录中不需要更改。|2104899|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/4220416/can-i-specify-multiple-users-for-myself-in-gitconfig/26170085#26170085^0|3|E|0|0|E|J|0|0|S|D|18|3|1W|A|27|B|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@$A|X|B|Y|1|Z]]|C|$]]|$1|D|3|E|5|6|7|10|8|@$A|11|B|12|F|G]]|9|@]|C|$]]|$1|H|3|I|5|J|7|13|8|@]|9|@]|C|$K|L]]|$1|M|3|N|5|6|7|14|8|@$A|15|B|16|F|G]|$A|17|B|18|F|G]|$A|19|B|1A|F|G]|$A|1B|B|1C|F|G]]|9|@]|C|$]]|$1|O|3|-4|5|6|7|1D|8|@]|9|@]|C|$]]]|P|$Q|$5|R|S|T|C|$U|V]]]]

Something like <a href="https://stackoverflow.com/questions/4220416/can-i-specify-multiple-users-for-myself-in-gitconfig/26170085#26170085">Rob W's answer</a>, but allowing different a different ssh key, and works with older git versions (which don't have e.g. a core.sshCommand config).

I created the file <code>~/bin/git_poweruser</code>, with executable permission, and in the PATH:

<pre><code>#!/bin/bash

TMPDIR=$(mktemp -d)
trap 'rm -rf "$TMPDIR"' EXIT

cat &gt; $TMPDIR/ssh &lt;&lt; 'EOF'
#!/bin/bash
ssh -i $HOME/.ssh/poweruserprivatekey $@
EOF

chmod +x $TMPDIR/ssh
export GIT_SSH=$TMPDIR/ssh

git -c user.name="Power User name" -c user.email="power@user.email" $@
</code></pre>

Whenever I want to commit or push something as "Power User", I use <code>git_poweruser</code> instead of <code>git</code>. It should work on any directory, and does not require changes in <code>.gitconfig</code> or <code>.ssh/config</code>, at least not in mine.

blocks|key|21253|text|只需将此代码添加到~/.bash_profile中，即可在github.com的默认键之间切换|type|unstyled|depth|inlineStyleRanges|entityRanges|data|21254|#+Git+SSH+keys+swap
alias+work_git="ssh-add+-D++&&+ssh-add+-K+~/.ssh/id_rsa_work"
alias+personal_git="ssh-add+-D+&&+ssh-add+-K+~/.ssh/id_rsa"|code-block|syntax|javascript|21255|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Just add this to your ~/.bash_profile to switch between default keys for github.com

<pre><code># Git SSH keys swap
alias work_git="ssh-add -D &amp;&amp; ssh-add -K ~/.ssh/id_rsa_work"
alias personal_git="ssh-add -D &amp;&amp; ssh-add -K ~/.ssh/id_rsa"
</code></pre>

blocks|key|1362315|text|有多种方法可以做到这一点，但我通过下面的shell函数来实现这一点。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1362316|​|1362317|function+gitprofile()+{
++++if+[[+$1+==+"private"+]];+then
++++++++if+grep+-q+"tom@workmail.com"+"/Users/tomtaylor/.gitconfig";+then
++++++++++++echo+"Found+in+gitconfig.+No+action+required."
++++++++else+
++++++++++++echo+"Found+in+gitconfig1"
++++++++++++cp+/Users/tomtaylor/.gitconfig+/Users/tomtaylor/.gitconfig2
++++++++++++mv+/Users/tomtaylor/.gitconfig1+/Users/tomtaylor/.gitconfig
++++++++++++mv+/Users/tomtaylor/.gitconfig2+/Users/tomtaylor/.gitconfig1
++++++++fi
++++elif+[[+$1+==+"public"+]];+then
++++++++if+grep+-q+"tom@gmail.com"+"/Users/tomtaylor/.gitconfig";+then
++++++++++++echo+"Found+in+gitconfig.+No+action+required."
++++++++else+
++++++++++++echo+"Found+in+gitconfig1"
++++++++++++cp+/Users/tomtaylor/.gitconfig+/Users/tomtaylor/.gitconfig2
++++++++++++mv+/Users/tomtaylor/.gitconfig1+/Users/tomtaylor/.gitconfig
++++++++++++mv+/Users/tomtaylor/.gitconfig2+/Users/tomtaylor/.gitconfig1
++++++++fi
++++else+
++++++++echo+"Nothing+matched.+Have+some+good+sleep!"
++++fi
}|code-block|syntax|javascript|1362318|1362319|像这样调用它，|1362320|gitprofile+"public“->这将切换到profile+with+tom@gmail.com和|offset|length|style|CODE|1362321|gitprofile+"private“->这将切换到tom@workmail.com。|1362322|根据您当前的终端首选项，将此函数添加到您的~/.bash_profile或~/.zshc。重新启动终端或只编译脚本，如下所示|1362323|1362324|。~/..bash_profile|blockquote|1362325|1362326|1362327|以使该函数有效。希望它能帮上忙！|1362328|entityMap^0|0|0|0|0|0|13|D|0|R|G|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|15|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|16|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|17|8|@]|9|@]|A|$G|H]]|$1|I|3|C|5|6|7|18|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|19|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|1A|8|@$N|1B|O|1C|P|Q]]|9|@]|A|$]]|$1|R|3|S|5|6|7|1D|8|@$N|1E|O|1F|P|Q]]|9|@]|A|$]]|$1|T|3|U|5|6|7|1G|8|@]|9|@]|A|$]]|$1|V|3|-4|5|6|7|1H|8|@]|9|@]|A|$]]|$1|W|3|X|5|Y|7|1I|8|@]|9|@]|A|$]]|$1|Z|3|-4|5|6|7|1J|8|@]|9|@]|A|$]]|$1|10|3|-4|5|6|7|1K|8|@]|9|@]|A|$]]|$1|11|3|12|5|6|7|1L|8|@]|9|@]|A|$]]|$1|13|3|-4|5|6|7|1M|8|@]|9|@]|A|$]]]|14|$]]

There can be multiple ways to do this, but I'm achieving this via the below shell function.
<div class="snippet" data-lang="js" data-hide="false" data-console="true" data-babel="false">
<div class="snippet-code">
<pre class="snippet-code-html lang-html prettyprint-override"><code>function gitprofile() {
 if [[ $1 == "private" ]]; then
 if grep -q "tom@workmail.com" "/Users/tomtaylor/.gitconfig"; then
 echo "Found in gitconfig. No action required."
 else 
 echo "Found in gitconfig1"
 cp /Users/tomtaylor/.gitconfig /Users/tomtaylor/.gitconfig2
 mv /Users/tomtaylor/.gitconfig1 /Users/tomtaylor/.gitconfig
 mv /Users/tomtaylor/.gitconfig2 /Users/tomtaylor/.gitconfig1
 fi
 elif [[ $1 == "public" ]]; then
 if grep -q "tom@gmail.com" "/Users/tomtaylor/.gitconfig"; then
 echo "Found in gitconfig. No action required."
 else 
 echo "Found in gitconfig1"
 cp /Users/tomtaylor/.gitconfig /Users/tomtaylor/.gitconfig2
 mv /Users/tomtaylor/.gitconfig1 /Users/tomtaylor/.gitconfig
 mv /Users/tomtaylor/.gitconfig2 /Users/tomtaylor/.gitconfig1
 fi
 else 
 echo "Nothing matched. Have some good sleep!"
 fi
}</code></pre>
</div>
</div>

Invoking it like,
gitprofile &quot;public&quot; -&gt; This would switch to profile with <code>tom@gmail.com</code> and
gitprofile &quot;private&quot; -&gt; This would switch to <code>tom@workmail.com</code>.
Add this function to your ~/.bash_profile or ~/.zshrc based on your current terminal preference. Restart the terminal or just compile the script like
<blockquote>
. ~/.bash_profile
</blockquote>
to make the function effective. Hope it helps !

blocks|key|21350|text|让我们重新定义一下规范--你只想通过git在不同的组织中使用多个身份--你所需要的就是2个oneliners：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|21351|+#+generate+a+new+private+public+key+pair+for+org1++
+email=me@org1.eu;ssh-keygen+-t+rsa+-b+4096+-C+$email+-f+$HOME/.ssh/id_rsa.$email

+#+use+org1+auth+in+THIS+shell+session+-+Ctrl+%2B+R,+type+org1+in+new+one+
+email=me@org1.eu;export+GIT_SSH_COMMAND="ssh+-p+22+-i+~/.ssh/id_rsa.$email"|code-block|syntax|javascript|21352|为什么我知道这是目前为止最简单的解决方案：|21353|++#+me+using+9+different+orgs+with+separate+git+auths+dynamically
++find+$HOME/.ssh/id_rsa.*@*+%7C+wc+-l
++18|21354|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

Let's redefine the specs - you just want to be able to use multiple identities with git against different organisations - all you need is 2 oneliners:
<pre><code> # generate a new private public key pair for org1 
 email=me@org1.eu;ssh-keygen -t rsa -b 4096 -C $email -f $HOME/.ssh/id_rsa.$email

 # use org1 auth in THIS shell session - Ctrl + R, type org1 in new one 
 email=me@org1.eu;export GIT_SSH_COMMAND=&quot;ssh -p 22 -i ~/.ssh/id_rsa.$email&quot;
</code></pre>
Why I know that this is by far the most simple solution:
<pre><code> # me using 9 different orgs with separate git auths dynamically
 find $HOME/.ssh/id_rsa.*@* | wc -l
 18
</code></pre>

In my <code>~/.gitconfig</code>, I list my personal email address under <code>[user]</code>, since that's what I want to use for Github repos.

But, I've recently started using git for work, too. My company's git repo allows me to commit, but when it sends out announcements of new changesets, it says they are from Anonymous because it doesn't recognize the email address in my <code>.gitconfig</code> - at least, that's my theory.

Is it possible to specify multiple <code>[user]</code> definitions in <code>.gitconfig</code>? Or is there some other way to override the default <code>.gitconfig</code> for a certain directory? In my case, I check out all work code in <code>~/worksrc/</code> - is there a way to specify a <code>.gitconfig</code> for only that directory (and its subdirectories)?

Can I specify multiple users for myself in .gitconfig?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

在我的~/.gitconfig中，我在[user]下列出了我的个人电子邮件地址，因为这就是我想要用于Github repos的地址。但是，我最近也开始在工作中使用git。我的公司的git repo允许我提交，但当它发出新变更集的公告时，它会说它们来自匿名，因为它无法识别我.gitconfig中的电子邮件地址-至少，这是我的理论。是否可以在.gitconfig中指定多个[user]定义？或者，是否有

问我可以在.gitconfig中为自己指定多个用户吗？
EN

回答 23

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问我可以在.gitconfig中为自己指定多个用户吗？EN

回答 23

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问我可以在.gitconfig中为自己指定多个用户吗？
EN