WordPress/gutenberg

Original PRs may not be tagged properly when a manual cherry-pick is performed.

Open

#76579 opened on Mar 17, 2026

View on GitHub
 (6 comments) (0 reactions) (2 assignees)JavaScript (9,607 stars) (3,893 forks)batch import
Good First Issue[Status] In Progress[Type] Build Tooling[Type] Enhancement

Description

What problem does this address?

When the automatic cherry-pick workflow fails for a given pull request, it can be easy to forget to add the Backported to label on the original PR once the one manually performing a git cherry-pick is performed. This can be problematic because the change may be left out of certain lists generated programatically.

What is your proposed solution?

It would be great if a manual cherry-pick command could be detected automatically when a pull request is merged to a wp/* or release/* branch and the original PR is labelled appropriately.

This may require a specific sentence to be included in the PR itself. It seems that closed PRs cannot be linked, but this would also work if possible.

Contributor guide

Tech stack
javascriptgithub actions
Domain
releaseci cd
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
GitHub Actionsshell scriptingcherry pick concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
This issue is assigned, indicating work is in progress. The proposed solution involves adding automatic detection of manual cherry picks, possibly by checking PR descriptions for a specific phrase or linking closed PRs. The existing cherry pick workflow is expected to be in a GitHub Actions file (e.g., `.github/workflows/cherry pick.yml`), which should be reviewed for integration points. Comments on the issue may provide further direction from maintainers.