Repository navigation
馃懛 ci(release): require changelog entries - #151
Merged
Merged
Conversation
gaborbernat
added
skip news
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Python-discovery can merge a PR without a news fragment, and its tag workflow can publish a version missing from the changelog.
This adds a Towncrier fragment check and collects it with the test jobs in one branch status.
skip newsexempts internal changes. Release preparation builds the changelog without a write credential; a separate job validates the patch before the repository App commits and tags it. The tag workflow checks the version indocs/changelog.rstbefore building distributions.The App key and branch and tag rulesets need to be configured after the code PR is ready.