Add Repository::getSymbolicRefTarget and Repository::getRemoteHead - #7
Merged
Conversation
|
LGTM, I'm happy to use it in my branch once merged or do you want to go about it? |
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
2 participants
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.
The discussion in pulsar-edit/ppm#175 revealed a use for a
git-utilsequivalent of the shell commandgit symbolic-ref. I also added agetRemoteHeadconvenience method that, given the name of origin, returns that origin's default branch ref.Specs were a bit tricky, but I did rely on Claude to help me create a new
.gitrepo to use as a fixture — one whose default branch name isdeveloprather thanmasterormain. Specs pass on my machine.