If you are like me and work for different companies, have several side hustles and fun projects, you will probably have the same problem as I have:
You want to use different configurations, like E-Mail Addresses, for those repositories.
Of course, you can always apply a local configuration to each repository or even use some scripts or aliases to help you out. But again, if you are like me, you won’t be happy with it, because you will forget to apply it over and over again.
Git allows you to include external configuration-files based on conditions, like the current directory. With this in mind, the problem above is actually easily solvable.
First use different base-directories for each “area”, like your different work-places and personal stuff:
/home/me/ dev-work-a/ dev-work-b/ dev-personal/
Then create a .gitconfig-file for each of those areas:
/home/me/ .gitconfig (your main configuration) .gitconfig-work-a (specific configuration for work a) .gitconfig-work-b (specific configuration for work b) .gitconfig-personal (specific configuration for personal projects)
In your main .gitconfig-File, instead of the actual values, you conditionally include the other files:
# ~/.gitconfig [includeIf "gitdir:~/dev-work-a/"] path = .gitconfig-work-a [includeIf "gitdir:~/dev-work-b/"] path = .gitconfig-work-b [includeIf "gitdir:~/dev-personal/"] path = .gitconfig-personal
and in the specific files, you just define the specific configuration values:
# ~/.gitconfig-work-a [user] name = Scooby Doo email = firstname.lastname@example.org
# ~/.gitconfig-work-b [user] name = Scooby Doo, Food-Department email = email@example.com
# ~/.gitconfig-personal [user] name = Scooby email = firstname.lastname@example.org
That’s basically it. So now, when you are for example in
~/dev-personal/bigbang-side-hustle Git will get your user-configuration from
Well, of course, you cannot use conditional configuration for user-configurations like name and e-mail only, it’s just a very common use case. But in fact, you can use it for whatever configuration you like.
There are also two more conditions like
onbranchlets you apply configurations based on the branch you are on
gitdir, but case-insensitive