Closed
Conversation
5cff7ab to
2f7378a
Compare
Contributor
Author
|
oh i see visualstudio has already been added :) |
2f7378a to
2fa04d8
Compare
Owner
|
Thanks for the contribution. Can you split these changes into two pull requests, please? One for the Azure DevOps change, and another for the default branch change. That will make it easier to review and merge. Thanks. |
2fa04d8 to
6ba265e
Compare
Contributor
Author
|
Done. Second PR: #27 |
Owner
|
Thanks. I like the idea of using I should have some time this later week to look into this further. I'll see if I can find a good way to do it. 😄 |
Owner
|
Implemented in 9fbba6b and available in v2.5.0. Thanks for your help! 😄 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hello :)
My personal favorite option is default branch. But we have many repositories and the default name is different everywhere: master, dev, develop, release, qa...
I suggest getting the default branch name as
origin/HEADwith the same command that gets the branch name forHEAD. This works fine with therev-parse --abbrev-ref, but I'm not sure how it would work with thesymbolic-ref