fix: Original PRs may not be tagged properly when a manual cherry-pick i#76655
fix: Original PRs may not be tagged properly when a manual cherry-pick i#76655JiwaniZakir wants to merge 2 commits intoWordPress:trunkfrom
Conversation
…76579) When a PR is merged to a wp/* or release/* branch and its title or body contains a cherry-pick reference (e.g. "cherry-picked from WordPress#12345"), automatically add the "Backported to WP Core" label to the original PR.
|
Warning: Type of PR label mismatch To merge this PR, it requires exactly 1 label indicating the type of PR. Other labels are optional and not being checked here.
Read more about Type labels in Gutenberg. Don't worry if you don't have the required permissions to add labels; the PR reviewer should be able to help with the task. |
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the Unlinked AccountsThe following contributors have not linked their GitHub and WordPress.org accounts: @JiwaniZakir. Contributors, please read how to link your accounts to ensure your work is properly credited in WordPress releases. If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
github-actions
bot
added
the
First-time Contributor
|
👋 Thanks for your first Pull Request and for helping build the future of Gutenberg and WordPress, @JiwaniZakir! In case you missed it, we'd love to have you join us in our Slack community. If you want to learn more about WordPress development in general, check out the Core Handbook full of helpful information. |
1 participant
Fixes #76579
When a manual cherry-pick is merged to a
wp/**orrelease/**branch, the original trunk PR was never labeled, leaving it untracked. No automated workflow existed to detect cherry-picks and apply labels. Adds.github/workflows/label-manual-cherry-pick.yml, which triggers onpull_request_targetclosed events, parses the PR title and body for cherry-pick references via regex, verifies the referenced PR targetstrunk, and applies theBackported to WP Corelabel.