New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for .gitconfig conditional includes #30
Comments
I'm also using several git configs and would appreciate if sublime merge could evaluate conditional includes to show the right git identity based on the working directory. At the moment when you put a |
Please support this! (I came to file a ticket, but searched first like a responsible developer 😉) Today I set up conditional includes to manage different identities under me This should be relatively straight-forward. I'm not sure how |
No more words needed. |
Support for conditional includes was added in build 1103 |
Hu ? I'm using Sublime Merge on Linux (Stable Channel, Build 1107) and it's clearly not there, or not working at all :) |
If it's not working for you, please file a new issue, and include the output of the Help/Debug Information menu item (removing any confidential parts first). |
Done @ #502 |
Problem description
I use conditional includes to separate my personal projects from work for my employer. Because of this, my
.gitconfig
doesn't directly contain a[user]
section; it's included dynamically based on the folder I'm working in:In
.gitconfig
.gitconfig-work
.gitconfig-personal
However, this results in Sublime Merge asking me to enter my name and email address when I commit to any repository, presumably because it can't find them in
.gitconfig
and isn't parsing the conditionals.As a result, I can't currently use SM at all, unless I re-specify my credentials for every repository I work on and persist them to the settings for the individual working copy.
Preferred solution
Sublime Merge should be able to figure out that the current repository is using conditionally included user info. I realise mine is a fairly niche use case, but it would be great to get support for this, as it is an established Git feature.
The text was updated successfully, but these errors were encountered: