Require Semantic Version labels on PR#1749
Merged
thomasvl merged 1 commit intoapple:mainfrom Jan 24, 2025
Merged
Conversation
# Motivation In most of our other Swift Server related repos we have introduced a new labelling system that allows us to use the GitHub auto-generated release notes. With those labels the release notes are properly grouped into their SemVer impact. # Modification This PR adds a new pipeline that makes sure each PR has the appropriate label set before it is merged. # Result No more PRs without SemVer classification.
gjcairo
approved these changes
Jan 24, 2025
Collaborator
|
I guess it works since it forced this PR to need a label also. 😄 |
Collaborator
|
Is there a way when preping a release to see the tagging on the PRs the commits came from to help figure out what sorta version bump is needed? |
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
3 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.
Motivation
In most of our other Swift Server related repos we have introduced a new labelling system that allows us to use the GitHub auto-generated release notes. With those labels the release notes are properly grouped into their SemVer impact.
Modification
This PR adds a new pipeline that makes sure each PR has the appropriate label set before it is merged.
Result
No more PRs without SemVer classification.