Conversation
Member
|
To throw out another option, what about naming property |
Member
|
IIRC git also calls it the "human-friendly name". In libgit2 itself we call it "shorthand" which to me conveys more of the semantic meaning. |
Member
Author
|
Let's go with |
Member
Author
|
Friendlier? |
LibGit2Sharp/ReferenceWrapper.cs
Outdated
nulltoken
changed the title
nulltoken
added a commit
that referenced
this pull request
Apr 15, 2015
Obsolete ReferenceWrapper.Name in favor of FriendlyName
Member
Author
|
Published as NuGet pre-release package |
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
3 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.
@jamill rightfully pointed at the fact that
Namewas maybe not explicit enough for aBranchor aTag.This PR is proposal to work around this by explicitly stating that this is a shortened version of the complete canonical name.
Thoughts?