release-draft-config.yml: Add breaking changes section#120
Merged
makubacki merged 1 commit intoFeb 7, 2023
Merged
Conversation
os-d
approved these changes
Feb 6, 2023
os-d
left a comment
os-d
left a comment
There was a problem hiding this comment.
Great, I was just about to file an issue for this :)
Breaking changes are identified with the GitHub label: `impact:breaking-change` Prior to this change, that label rolled the major version of the repo. Now, the label also places corresponding changes into a "Breaking Changes" section of the release notes so it is easy for consumers to see breaking changes in a release. Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
makubacki
force-pushed
the
add_breaking_changes_section_to_release_note_drafter
branch
from
85aa22f to
15c4093
Compare
kenlautner
approved these changes
Feb 7, 2023
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.
Closes #119
Breaking changes are identified with the GitHub label:
impact:breaking-changePrior to this change, that label rolled the major version of the
repo.
Now, the label also places corresponding changes into a "Breaking
Changes" section of the release notes so it is easy for consumers
to see breaking changes in a release.
Signed-off-by: Michael Kubacki michael.kubacki@microsoft.com