chore: Add a workflow to check the presence of release notes #5449
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
masci
added
the
ignore-for-release-notes
anakin87
approved these changes
Jul 27, 2023
masci
changed the title
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.
Related Issues
ignore-for-release-notes#5426Proposed Changes:
Add a workflow that checks for the presence of a
.yamlfile in thereleasenotes/notesfolder in each PR. The check is skipped if the PR has theignore-for-release-noteslabel attached.How did you test it?
Manually tested on a different repo
Notes for the reviewer
This check doesn't validate the actual content of the release notes, this might be a nice-to-have follow up.
Checklist
fix:,feat:,build:,chore:,ci:,docs:,style:,refactor:,perf:,test:.