-
I am using the default GitVersion setup with For some reason GitVersion chose So I have three questions:
|
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 6 replies
-
Whenever someone is experiencing versioning issues, I always recommend removing |
Beta Was this translation helpful? Give feedback.
-
@asbjornu Even without a
So I have created several tagged preview releases on %%{init: { 'logLevel': 'debug', 'theme': 'base', 'gitGraph': {'showCommitLabel':false}} }%%
gitGraph
commit
branch develop
commit
commit
branch release/1.0.0
checkout release/1.0.0
commit tag: "1.0.0-beta.1"
commit
commit tag: "1.0.0-beta.2"
commit
commit tag: "1.0.0-beta.3"
commit
commit tag: "1.0.0-beta.4"
commit
commit tag: "1.0.0-beta.5"
checkout develop
merge release/1.0.0
commit
commit
commit
checkout release/1.0.0
commit
Could this be the reason why it chose |
Beta Was this translation helpful? Give feedback.
-
I think I have finally understood why this happens. |
Beta Was this translation helpful? Give feedback.
I think I have finally understood why this happens.
Whenever there are commits on
develop
that are not yet onrelease\1.0.0
, GitVersion chooses1.1.0-aphaX
as the version numberon
develop
.But as soon as
release/1.0.0
is merged intodevelop
(or the other way around), it goes back to1.0.0-aphaY
ondevelop
.Even though I understand why GitVersion does this, it raises the question how the default workflow is ever going to work: #3177