Add new workflow to fixup backports for release notes #3252
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
jackkoenig
added
the
Internal
mwachs5
approved these changes
May 5, 2023
|
It works 🙂 |
The Mergify-generated backports do not currently include the information needed by the release notes generation automation. This new workflow will copy such information over to backport PRs.
mergify bot
pushed a commit
that referenced
this pull request
May 5, 2023
The Mergify-generated backports do not currently include the information needed by the release notes generation automation. This new workflow will copy such information over to backport PRs. (cherry picked from commit 86ccd1b)
mergify bot
pushed a commit
that referenced
this pull request
May 5, 2023
The Mergify-generated backports do not currently include the information needed by the release notes generation automation. This new workflow will copy such information over to backport PRs. (cherry picked from commit 86ccd1b)
This was referenced May 5, 2023
|
See how the backport PRs created from this PR are labeled and had the body of the PR message copied over. |
|
Although it doesn't work for labels with spaces in them 😑, Will fix |
mergify bot
added a commit
that referenced
this pull request
May 5, 2023
#3254) * Add new workflow to fixup backports for release notes (#3252) The Mergify-generated backports do not currently include the information needed by the release notes generation automation. This new workflow will copy such information over to backport PRs. (cherry picked from commit 86ccd1b) * Fix backport-fixup for labels with spaces (#3255) (cherry picked from commit 8f7e7e6) --------- Co-authored-by: Jack Koenig <koenig@sifive.com>
mergify bot
added a commit
that referenced
this pull request
May 5, 2023
#3253) * Add new workflow to fixup backports for release notes (#3252) The Mergify-generated backports do not currently include the information needed by the release notes generation automation. This new workflow will copy such information over to backport PRs. (cherry picked from commit 86ccd1b) * Fix backport-fixup for labels with spaces (#3255) (cherry picked from commit 8f7e7e6) --------- Co-authored-by: Jack Koenig <koenig@sifive.com>
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.
The Mergify-generated backports do not currently include the information needed by the release notes generation automation. This new workflow will copy such information over to backport PRs.
Contributor Checklist
docs/src?Type of Improvement
Desired Merge Strategy
Release Notes
Improve backport automation so that release notes generation from backport PRs works properly.
Reviewer Checklist (only modified by reviewer)
3.5.xor3.6.xdepending on impact, API modification or big change:5.0.0)?Enable auto-merge (squash), clean up the commit message, and label withPlease Merge.Create a merge commit.