Skip to content
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

Support differentiating multiple branches #15

Closed
jola5 opened this issue Jul 7, 2017 · 0 comments
Closed

Support differentiating multiple branches #15

jola5 opened this issue Jul 7, 2017 · 0 comments
Assignees
Labels

Comments

@jola5
Copy link
Owner

jola5 commented Jul 7, 2017

Sometimes you work on projects where different branches are used for specific releases. Imagine a repository with a mature 1.9.21 release and an according branch and a brand new 2.0.3 release with according branch.

If you need to provide bugfixes and security updates for your 1.9.21 release you still need to create new minor and patch versions like 1.9.22. This is a typical use case and the git describe command works exactly as expected by returning the most git tag on this particular branch. Gtv on the other hand does not support this use case since we only update on the most recent version tag - which is 2.0.3. You can circumvent this by specifically setting a version to a specific commit with gtv set 1.9.22 abcdef987456 but the whole point of gtv is to simplify working with version tags.

Therefore, this request proposes a change so gtv works like git describe

# working on 1.x release
git checkout release_1.x.x
git describe
v1.9.21
git tag-version
2.0.3
# add a new patch to this specific release/branch
git tag-version new patch
git describe
v2.0.4
git tag-version
2.0.4
# switch to 2.x release
git checkout release_2.x.x
git describe
v2.0.3
git tag-version
2.0.4

The current implementation's behaviour is quirky, unexpected and undocumented as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant