feat: Force user to follow the rule of release note generation #385
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
0Tech
previously approved these changes
May 28, 2024
0Tech
approved these changes
May 28, 2024
zemyblue
approved these changes
Jun 12, 2024
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
closes: #XXXX
RELEASE_DESCRandCHANGELOGfor all tags from now. We allowed to not write those sections sometimes and worked as best effort (getting latest previous content instead of exact previous tag content if we can't find). I decided to apply this rule to avoid confusion during release process.Motivation and context
How has this been tested?
Screenshots (if appropriate):
Checklist:
CHANGELOG.md