Elaborate on next-version
#2963
Merged
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
Elaborate on `next-version` and explain how it's not a replacement for `git tag`.
arturcic
approved these changes
Jan 18, 2022
Contributor
|
Thank you @asbjornu for your contribution! |
arturcic
pushed a commit
that referenced
this pull request
Jan 18, 2022
Merge pull request #2963 from asbjornu/feature/next-version Elaborate on `next-version`
|
🎉 This issue has been resolved in version 5.8.2 🎉 Your GitReleaseManager bot 📦🚀 |
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.
Description
Elaborate on
next-versionand explain how it's not a replacement forgit tag.Related Issue
#2441, #2454, #2461, #2467, #2610, #2661, #2670, #2694 and #2940.
Motivation and Context
In #2441 and many duplicate and related issues, there has been uncovered confusion about what
next-versionactually means and how it's supposed to be used. This PR adds more information about hownext-versionis supposed to be used and that removing it entirely from the configuration may resolve versioning problems people experience.Checklist: