Align the Configuration reference documentation with the code #2914
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
asbjornu
requested changes
Nov 11, 2021
asbjornu
approved these changes
Nov 11, 2021
|
Thank you @chris-codeflow for your contribution! |
chris-codeflow
deleted the
feature/Align-configuration-reference-doc-with-code
branch
|
When does the https://gitversion.net site get synced with the published documentation @asbjornu or @arturcic? |
|
It should be published on next planned release |
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
Related Issue
Closes #2913
Motivation and Context
My motivation for submitting this PR was due to when I found that GitVersion was using a pre-release label (tag) of
alphawhen calculating the SemVer in adevelopbranch, but the reference documentation stated the pre-release label should beunstable. After checking the latest source code in themainbranch, I found that the documentation was not fully aligned with the source code.How Has This Been Tested?
Triple-checked the changes against the source code.
Screenshots (if appropriate):
N/A
Checklist: