Skip to content
This repository has been archived by the owner on Feb 3, 2018. It is now read-only.

Prioritize branches above non-semver tags #98

Closed
sdboyer opened this issue Sep 14, 2016 · 1 comment
Closed

Prioritize branches above non-semver tags #98

sdboyer opened this issue Sep 14, 2016 · 1 comment
Assignees
@sdboyer
Labels
correctness
Milestone
v0.11.0

Comments

@sdboyer
Copy link
Owner

sdboyer commented Sep 14, 2016

Sort ordering needs to change to prefer branches above non-semver tags. In another lang community, that might not be sane, but the strong tendency towards the 'default branch' established by go get means it's what makes sense here.
@sdboyer sdboyer added this to the v0.11.0 milestone Sep 14, 2016
@sdboyer sdboyer self-assigned this Sep 14, 2016
@sdboyer
Copy link
Owner Author

sdboyer commented Sep 14, 2016

The need to do this is also noted in #65

@sdboyer sdboyer mentioned this issue Sep 14, 2016
Open
10 tasks
@sdboyer sdboyer mentioned this issue Sep 15, 2016
Closed
krisnova pushed a commit to krisnova/dep that referenced this issue Apr 21, 2017
@sdboyer
Prioritize branches above non-semver tags/versions
0f41413 
In another language community this might make less sense, but years of
`go get` has created a strong precedent around branch use, so this makes
more sense.

Fixes sdboyer/gps#98.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@sdboyer sdboyer

Labels
correctness
Projects
None yet
Milestone
v0.11.0
Development

No branches or pull requests
1 participant
@sdboyer