GitVersion calculates the wrong version after main is merged back to develop #3927
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
HHobeck
force-pushed
the
feature/GitVersion-calculates-the-wrong-version
branch
2 times, most recently
from
0ce2b07
to
567274a
Compare
arturcic
force-pushed
the
feature/GitVersion-calculates-the-wrong-version
branch
from
567274a
to
a0c170b
Compare
|
Thank you @HHobeck for your contribution! |
|
@HHobeck for some reason when the build is performed for the PR the issue appears, but when it's run as a branch not linked to a PR, it runs without problems. Might be the name of the PR branch has some issues |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Close #3699
Motivation and Context
Fix GitVersion calculates the wrong version after main is merged back to develop
Checklist: