-
Notifications
You must be signed in to change notification settings - Fork 649
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 specific branches for tracking versions #452
Comments
The reason this issue is being created is that commit 5, 6, 8 will never go into the 2.2.0 release, but do get the 2.2.0-unstable versioning. Another option is to manually bump nextversion in gitversionconfig. |
This is the class which tracks master. Ideally we could extend this class to also track release branches, maybe even in a generic way |
It gets even worse. We released 2.2.0 today, then the same commit (which was already numbered 2.2.0-unstable7 (but actually should be 2.3.0-unstable1) now becomes 2.3.0-unstable1 (but it's the same commit). |
See #465 I am trying to figure out how to solve this problem. Ideas are welcome |
@GeertvanHorrik my PR should fix the last issue you posted about. Want to give it a spin? |
Definitely. I was away last week so have to catch up with all e-mail, then will look into this. |
Writing a unit test for this scenario. |
I have this graph, all seems to work fine:
|
See PR #484 |
#452 Added unit tests for GitFlowScenarios
See this problem:
We had quite a few discussions about this, but to solve it, something like this might solve this issue:
How about, new branch config option trackVersion: release/
Then the version will be determined based on the following rules:
The text was updated successfully, but these errors were encountered: