Use the Inherit strategy by default #1085
Closed
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
…anches extension method.
The GitVersionContextBuilder does not create an actual repository, causing exceptions.
Contributor
|
Rebased then reopened at #1103 |
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.
Alternative implementation for PR #1004:
By default, branches without an explicit value for
incrementuse the valueInherit(this wasPatchbefore). If the default value should remain Patch, this can be easily changed in ConfigurationProvider.cs.The default value for
incrementcan be set "globally" in the config, just as can be done formode.Extended and clarified the documentation for increment and the version number sources.
Added a bunch of comments in the code and did some refactoring/cleanup.