Invalid release version after commit beetween merge release to develop #1593
Conversation
This file contains hidden or 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
asbjornu
force-pushed
the
feature/commit-beetween-merge-release-to-develop
branch
from
896bc1b to
2934138
Compare
asbjornu
deleted the
feature/commit-beetween-merge-release-to-develop
branch
asbjornu
added a commit
to asbjornu/GitVersion
that referenced
this pull request
Feb 20, 2019
…n-merge-release-to-develop Adds a test to ensure that a commit between merge-release to develop does not reset the commit count.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Adds a test to ensure that a commit between merge-release to develop does not reset the commit count. Rebase and conflict resolvement of #1205. Resolves #1205.