Add FAQ section on merged branch names as version source #2750
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
5 tasks
arturcic
approved these changes
Jul 12, 2021
Also clean up Version Incremnets a bit.
asbjornu
force-pushed
the
feature/faq-branch-names
branch
from
81b8a55
to
c2373fa
Compare
|
Thank you @asbjornu for your contribution! |
github-actions bot
pushed a commit
that referenced
this pull request
Jul 12, 2021
Merge pull request #2750 from asbjornu/feature/faq-branch-names Add FAQ section on merged branch names as version source
|
🎉 This issue has been resolved in version 5.6.11 🎉 Your GitReleaseManager bot 📦🚀 |
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.
Add FAQ section on merged branch names as version source.
Description
Since there's a continual stream of questions about using branch names as the source of version calculation, I've written up a FAQ section that hopefully clarifies this that we at least can point to in the future when the question arises again.
Related Issue
#2739, #2740.
Motivation and Context
See #2739 and the subsequent discussion in #2740 for a recent example of why an FAQ section on this is needed.
Checklist: