Skip to content

Why did GitVersion choose 1.0.0-alpha.4 in this case #3167

Answered by bitbonk
bitbonk asked this question in Q&A
Discussion options

You must be logged in to vote

I think I have finally understood why this happens.
Whenever there are commits on develop that are not yet on release\1.0.0 , GitVersion chooses 1.1.0-aphaX as the version number
on develop.
But as soon as release/1.0.0 is merged into develop (or the other way around), it goes back to 1.0.0-aphaY on develop.
Even though I understand why GitVersion does this, it raises the question how the default workflow is ever going to work: #3177

Replies: 3 comments 6 replies

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
6 replies
@bitbonk
Comment options

@asbjornu
Comment options

@bitbonk
Comment options

@asbjornu
Comment options

@bitbonk
Comment options

Answer selected by bitbonk
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants