-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Add support for the new includeIf directive #315
Comments
GitUp relies on https://libgit2.github.com/, is it supported there? |
Probably not. A quick skim doesn't suggest anything like this has been added since Git 2.13 came out. I'll file a ticket on them. |
Filed as libgit2/libgit2#4246. |
Thanks! |
libgit2 just implemented this. I'd love to see a GitUp update that includes this change. |
I'm considering fixing this. Would somebody be able to point me in the right direction? I have never seen this code base before, and neither that of libgit2, so few pointers / suggestions would be very welcome. |
Oops, the git-up/libgit2 fork: "This branch is 73 commits ahead, 2334 commits behind libgit2:master". I don't think I'm going to be able to fix that. I quickly tried to rebase / merge but that gives too many conflicts for me to solve. |
I would be happy to see this too. A practical use case: My default
to override it with work address on work projects below that path. Currently if I make commits with GitUp on work projects, they will use with my personal address. |
Are we able to straight up use https://github.com/libgit2/libgit2, if it already supports the customizations made by the git-up/libgit2 fork? Thanks. |
I believe the includeIf directive now should be understood in 1.3.3 (because of the libgit2 bump) which is now on the continuous channel. I'm going to close out this issue, but if this isn't resolved, please feel free to reopen. |
That's great news @lucasderraugh, thanks!! Does that (libgit2 bump) mean that gitup now also performs code signing, or is that unrelated? |
I understand, thanks for clarifying! |
Git 2.13 added a new feature where your config can have an
includeIf.<condition>.path
directive that acts likeinclude.path
as long as the condition holds. It looks like GitUp doesn't understand this.The text was updated successfully, but these errors were encountered: