Shulou(Shulou.com)06/01 Report--

This article is about software adapting Git configuration to meet the needs of multiple users'ID. The editor thinks it is very practical, so share it with you as a reference and follow the editor to have a look.

You can use the same machine for both work and personal Git submissions without having to manually reset your configuration.

Git's git config command allows you to set repository or global options for Git. It has many options, one of which, includeIf, is very convenient when you have a dual role in Git, for example, you are a full-time developer and contribute to open source projects in your spare time. In this case, most people don't want to use a common configuration for two roles, or, at the very least, they definitely want to keep some parts of the configuration different, especially if they use the same computer in two roles.

This is my case, so I keep two different sets of mail ID in the Git configuration. In this way, the content submitted in my workplace project repository will use my office email ID, while the content submitted in my personal GitHub account will use my personal email ID.

The following is a snippet from my global configuration (maintained in $HOME/.gitconfig), which I'll cover later.

[includeIf "gitdir:~/priv_scm/"] path = ~ / priv_scm/ .gitconfig[ origindeIf "gitdir:~/work_scm/"] path = ~ / work_scm/.gitconfig what is includeIf?

The includeIf.condition.path variable, which is part of the include configuration instruction, allows you to conditionally set a custom configuration. At the same time, the path of the custom configuration can also be set as part of the instruction.

This instruction supports three keywords: gitdir, gitdir/I, and onbranch. I'll briefly explain gitdir, which I used in the code snippet above. You can learn about the other two keywords in the document.

Use the gitdir keyword in the includeIf instruction to conditionally check the pattern. According to the rule, if the current working directory matches the directory pattern specified in gitdir, it selects the configuration from the given path. I will apply this rule to the configuration snippet to show how it is applied.

In the configuration snippet, you can see a simple pattern, ~ /, used with the gitdir keyword. This pattern is replaced by a value stored in the $HOME environment variable.

How to use it

If you use the same system to work on an open source project on GitHub or GitLab and submit it to the Git repository at work, you can have two top-level directories, such as $HOME/priv_scm and $HOME/work_scm. In these two directories, you can have two separate .gitconfig files that contain settings related to your user.name and user.email. However, they can also be stored in the global .gitconfig of $HOME, which can hold all customizations common to both environments.

Here is a snippet of an example $HOME/priv_scm/.gitconfig:

$cat $HOME/priv_scm/ .gitconfig[ user] name = Ramanathan Muthiah email =

With this configuration, you can change directories and start working on open source projects without manually resetting some Git-related configurations. These changes are handled automatically in the master .gitconfig with the help of the includeIf conditional directive.

Thank you for reading! This is the end of this article on "Software adjusting Git configuration to meet the needs of multiple users'ID". I hope the above content can be of some help to you, so that you can learn more knowledge. if you think the article is good, you can share it out for more people to see!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.