blocks|key|469259|text|存储库特定克隆中的.git/config文件是该克隆的本地文件。其中的任何设置都只会影响该特定项目的操作。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|469260|(默认情况下，git+config修改.git/config，而不是~/.gitconfig+-只有在使用--global时，它才会修改后者。)|469261|entityMap^0|9|B|0|7|A|J|B|Y|C|1H|8|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@$9|N|A|O|B|C]|$9|P|A|Q|B|C]|$9|R|A|S|B|C]|$9|T|A|U|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|V|8|@]|D|@]|E|$]]]|I|$]]

The <code>.git/config</code> file in a particular clone of a repository is local to that clone. Any settings placed there will only affect actions for that particular project.

(By default, <code>git config</code> modifies <code>.git/config</code>, not <code>~/.gitconfig</code> - only with <code>--global</code> does it modify the latter.)

blocks|key|685481|text|从git版本2.13开始，git支持conditional+configuration+includes。在本例中，我们在~/company_a目录中克隆公司A的repos，在~/company_b目录中克隆公司B的repos。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|685482|在你的.gitconfig中，你可以放一些类似这样的东西。|685483|[includeIf+"gitdir:~/company_a/"]
++path+=+.gitconfig-company_a
[includeIf+"gitdir:~/company_b/"]
++path+=+.gitconfig-company_b|code-block|syntax|javascript|685484|.gitconfig+company_a的示例内容|685485|[user]
name+=+John+Smith
email+=+john.smith@companya.net|685486|.gitconfig+company_b的示例内容|685487|[user]
name+=+John+Smith
email+=+js@companyb.com|685488|entityMap|0|LINK|mutability|MUTABLE|url|https://git-scm.com/docs/git-config#_includes^0|1P|B|2G|B|I|Y|0|0|3|A|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@$9|13|A|14|B|C]|$9|15|A|16|B|C]]|D|@$9|17|A|18|1|19]]|E|$]]|$1|F|3|G|5|6|7|1A|8|@$9|1B|A|1C|B|C]]|D|@]|E|$]]|$1|H|3|I|5|J|7|1D|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|1E|8|@]|D|@]|E|$]]|$1|O|3|P|5|J|7|1F|8|@]|D|@]|E|$K|L]]|$1|Q|3|R|5|6|7|1G|8|@]|D|@]|E|$]]|$1|S|3|T|5|J|7|1H|8|@]|D|@]|E|$K|L]]|$1|U|3|-4|5|6|7|1I|8|@]|D|@]|E|$]]]|V|$W|$5|X|Y|Z|E|$10|11]]]]

As of git version 2.13, git supports <a href="https://git-scm.com/docs/git-config#_includes" rel="noreferrer">conditional configuration includes</a>. In this example we clone Company A's repos in <code>~/company_a</code> directory, and Company B's repos in <code>~/company_b</code>.

In your <code>.gitconfig</code> you can put something like this.

<pre><code>[includeIf "gitdir:~/company_a/"]
 path = .gitconfig-company_a
[includeIf "gitdir:~/company_b/"]
 path = .gitconfig-company_b
</code></pre>

Example contents of .gitconfig-company_a

<pre><code>[user]
name = John Smith
email = john.smith@companya.net
</code></pre>

Example contents of .gitconfig-company_b

<pre><code>[user]
name = John Smith
email = js@companyb.com
</code></pre>

blocks|key|469431|text|我通过以下方式对我的电子邮件执行此操作：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|469432|git+config+--global+alias.hobbyprofile+'config+user.email+"me@example.com"'|code-block|syntax|javascript|469433|然后，当我克隆一个新的工作项目时，我只需要运行git+hobbyprofile，它将被配置为使用该电子邮件。|offset|length|style|CODE|469434|entityMap^0|0|0|N|G|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@$I|R|J|S|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

I am doing this for my email in the following way:

<pre><code>git config --global alias.hobbyprofile 'config user.email "me@example.com"'
</code></pre>

Then when I clone a new work project, I have only to run <code>git hobbyprofile</code> and it will be configured to use that email.

blocks|key|469535|text|另一种方法是使用direnv，并将每个目录的配置文件分开。例如：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|469536|.
├──+companyA
│++├──+.envrc
│++└──+.gitconfig
├──+companyB
│++├──+.envrc
│++└──+.gitconfig
└──+personal
+++├──+.envrc
+++└──+.gitconfig|code-block|syntax|javascript|469537|每个.envrc都应该包含如下内容：|style|CODE|469538|export+GIT_CONFIG_GLOBAL=$(pwd)/.gitconfig|469539|而.gitconfig通常是带有所需值的gitconfig。|469540|这是我在自定义.gitconfig文件中实际拥有的内容：|469541|[user]
++++email+=+my.name@company.com

[include]
++++path+=+~/.gitconfig|469542|这里只覆盖了user.email，rest配置取自默认的~/.gitconfig。|469543|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/direnv/direnv^0|8|6|0|0|0|2|6|0|0|1|A|0|7|A|0|0|6|A|S|C|0^^$0|@$1|2|3|4|5|6|7|14|8|@]|9|@$A|15|B|16|1|17]]|C|$]]|$1|D|3|E|5|F|7|18|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|19|8|@$A|1A|B|1B|K|L]]|9|@]|C|$]]|$1|M|3|N|5|F|7|1C|8|@]|9|@]|C|$G|H]]|$1|O|3|P|5|6|7|1D|8|@$A|1E|B|1F|K|L]]|9|@]|C|$]]|$1|Q|3|R|5|6|7|1G|8|@$A|1H|B|1I|K|L]]|9|@]|C|$]]|$1|S|3|T|5|F|7|1J|8|@]|9|@]|C|$G|H]]|$1|U|3|V|5|6|7|1K|8|@$A|1L|B|1M|K|L]|$A|1N|B|1O|K|L]]|9|@]|C|$]]|$1|W|3|-4|5|6|7|1P|8|@]|9|@]|C|$]]]|X|$Y|$5|Z|10|11|C|$12|13]]]]

Another way is to use <a href="https://github.com/direnv/direnv" rel="nofollow noreferrer">direnv</a> and to separate config files per directory. For example:
<pre><code>.
├── companyA
│ ├── .envrc
│ └── .gitconfig
├── companyB
│ ├── .envrc
│ └── .gitconfig
└── personal
 ├── .envrc
 └── .gitconfig
</code></pre>
Each <code>.envrc</code> should contain something like this:
<pre><code>export GIT_CONFIG_GLOBAL=$(pwd)/.gitconfig
</code></pre>
And <code>.gitconfig</code> is usual gitconfig with desired values.
This is what I actually have in the custom <code>.gitconfig</code> files:
<pre><code>[user]
 email = my.name@company.com

[include]
 path = ~/.gitconfig
</code></pre>
Here only <code>user.email</code> is overwritten, the rest configuration is taken from the default <code>~/.gitconfig</code>.

blocks|key|685347|text|您还可以将环境变量GIT_CONFIG指向git+config应该使用的文件。使用GIT_CONFIG=~/.gitconfig-A+git+config+key+value操作指定的文件。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|685348|entityMap^0|9|A|L|A|15|1A|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|O|8|@]|D|@]|E|$]]]|G|$]]

You can also point the environment variable <code>GIT_CONFIG</code> to a file that <code>git config</code> should use. With <code>GIT_CONFIG=~/.gitconfig-A git config key value</code> the specified file gets manipulated.

blocks|key|685605|text|您可以通过更改特定于存储库的配置文件(即/path/to/repo/.git/config)来自定义项目的Git配置。顺便说一句，默认情况下，git+config会写入此文件：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|685606|cd+/path/to/repo
git+config+user.name+'John+Doe'++#+sets+user.name+locally+for+the+repo|code-block|syntax|javascript|685607|我更喜欢为不同的项目创建单独的配置文件(例如，在~/.gitconfig.d/中)，然后在存储库的配置文件中对它们进行include：|685608|cd+/path/to/repo
git+config+include.path+'~/.gitconfig.d/myproject.conf'|685609|如果您需要在属于单个项目的多个repos中使用相同的选项集，则此方法效果很好。您还可以设置shell别名或自定义Git命令来操作配置文件。|685610|entityMap|0|LINK|mutability|MUTABLE|url|https://git-scm.com/docs/git-config|1|https://git-scm.com/docs/git-config#_includes^0|K|P|1Z|A|1Z|A|0|0|0|O|F|1N|7|1|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@$9|11|A|12|B|C]|$9|13|A|14|B|C]]|D|@$9|15|A|16|1|17]]|E|$]]|$1|F|3|G|5|H|7|18|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|19|8|@$9|1A|A|1B|B|C]]|D|@$9|1C|A|1D|1|1E]]|E|$]]|$1|M|3|N|5|H|7|1F|8|@]|D|@]|E|$I|J]]|$1|O|3|P|5|6|7|1G|8|@]|D|@]|E|$]]|$1|Q|3|-4|5|6|7|1H|8|@]|D|@]|E|$]]]|R|$S|$5|T|U|V|E|$W|X]]|Y|$5|T|U|V|E|$W|Z]]]]

You can customize a project's Git config by changing the repository specific configuration file (i.e. <code>/path/to/repo/.git/config</code>). BTW, <a href="https://git-scm.com/docs/git-config" rel="nofollow noreferrer"><code>git config</code></a> writes to this file by default:

<pre><code>cd /path/to/repo
git config user.name 'John Doe' # sets user.name locally for the repo
</code></pre>

I prefer to create separate profiles for different projects (e.g. in <code>~/.gitconfig.d/</code>) and then <a href="https://git-scm.com/docs/git-config#_includes" rel="nofollow noreferrer">include</a> them in the repository's config file:

<pre><code>cd /path/to/repo
git config include.path '~/.gitconfig.d/myproject.conf'
</code></pre>

This works well if you need to use the same set of options in multiple repos that belong to a single project. You can also set up shell aliases or a custom Git command to manipulate the profiles.

blocks|key|685388|text|我也是一样的。我写了一个小的bash脚本来管理它们。https://github.com/thejeffreystone/setgit|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|685389|#!/bin/bash

#+setgit
#
#+Script+to+manage+multiple+global+gitconfigs
#+
#+To+save+your+current+.gitconfig+to+.gitconfig-this+just+run:
#+setgit+-s+this
#
#+To+load+.gitconfig-this+to+.gitconfig+it+run:
#+setgit+-f+this
#+
#+
#+
#+Author:+Jeffrey+Stone+<thejeffreystone@gmail.com>

usage(){
++echo+"$(basename+$0)+[-h]+[-f+name]"+
++echo+""
++echo+"where:"
++echo+"+-h++Show+Help+Text"
++echo+"+-f++Load+the+.gitconfig+file+based+on+option+passed"
++echo+""
++exit+1++
}

if+[+$#+-lt+1+]
then
++usage
++exit
fi

while+getopts+':hf:'+option;+do
++case+"$option"+in
++++++h)+usage
+++++++++exit
+++++++++;;
++++++f)+echo+"Loading+.gitconfig+from+.gitconfig-$OPTARG"
+++++++++cat+~/.gitconfig-$OPTARG+>+~/.gitconfig
+++++++++;;
++++++*)+printf+"illegal+option:+'%25s'\n"+"$OPTARG"+>&2
+++++++++echo+"$usage"+>&2
+++++++++exit+1
+++++++++;;
++++esac
done|code-block|syntax|javascript|685390|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/thejeffreystone/setgit^0|Q|15|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@$A|R|B|S|1|T]]|C|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|C|$G|H]]|$1|I|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|J|$K|$5|L|M|N|C|$O|P]]]]

I'm in the same boat. I wrote a little bash script to manage them. 
<a href="https://github.com/thejeffreystone/setgit" rel="nofollow">https://github.com/thejeffreystone/setgit</a>

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

# setgit
#
# Script to manage multiple global gitconfigs
# 
# To save your current .gitconfig to .gitconfig-this just run:
# setgit -s this
#
# To load .gitconfig-this to .gitconfig it run:
# setgit -f this
# 
# 
# 
# Author: Jeffrey Stone &lt;thejeffreystone@gmail.com&gt;

usage(){
 echo "$(basename $0) [-h] [-f name]" 
 echo ""
 echo "where:"
 echo " -h Show Help Text"
 echo " -f Load the .gitconfig file based on option passed"
 echo ""
 exit 1 
}

if [ $# -lt 1 ]
then
 usage
 exit
fi

while getopts ':hf:' option; do
 case "$option" in
 h) usage
 exit
 ;;
 f) echo "Loading .gitconfig from .gitconfig-$OPTARG"
 cat ~/.gitconfig-$OPTARG &gt; ~/.gitconfig
 ;;
 *) printf "illegal option: '%s'\n" "$OPTARG" &gt;&amp;2
 echo "$usage" &gt;&amp;2
 exit 1
 ;;
 esac
done
</code></pre>

<code>.gitconfig</code> is usually stored in the <code>user.home</code> directory.

I use a different identity to work on projects for Company A and something else for Company B (primarily the name / email). How can I have two different Git configurations so that my check-ins don't go with the name / email?

Is it possible to have different Git configuration for different projects?

.gitconfig通常存储在user.home目录中。我使用不同的身份为公司A处理项目，为公司B处理其他项目(主要是名称/电子邮件)。我如何才能有两种不同的Git配置，以便我的签到不会使用名称/电子邮件？

问有没有可能对不同的项目有不同的Git配置？
EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问有没有可能对不同的项目有不同的Git配置？EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问有没有可能对不同的项目有不同的Git配置？
EN