Added support for NextVersion.txt in GitFlow and dynamic repositories #208
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
GitVersionExe/GitPreparer.cs
Outdated
There was a problem hiding this comment.
Nope, this is the only special file
There was a problem hiding this comment.
Great, will remove the comment
|
Looks good, thanks |
JakeGinnivan
added a commit
that referenced
this pull request
Jul 8, 2014
Added support for NextVersion.txt in GitFlow and dynamic repositories
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Note that this only applies to develop-based branches. Master branches are still retrieved correctly by using the tags, but this allows to override the next version on develop builds (so I can deploy 4.0.0-unstable0389 on the develop branch, otherwise it would have been 3.10.0-unstable0389).