WordPress/gutenberg

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

Open

#76.579 geöffnet am 17. März 2026

Auf GitHub ansehen
 (6 Kommentare) (0 Reaktionen) (2 zugewiesene Personen)JavaScript (9.607 Stars) (3.893 Forks)batch import
Good First Issue[Status] In Progress[Type] Build Tooling[Type] Enhancement

Beschreibung

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
SchwierigkeitGeschätzte Implementierungsschwierigkeit für neue Contributors, von 1 für sehr kleine Änderungen bis 5 für Expertenarbeit.
3
Geschätzte ZeitEin grober Zeitrahmen, um zu recherchieren, zu implementieren, zu testen und einen Pull Request vorzubereiten.
1-2 days
AktivitätsstatusWie verfügbar das Issue gerade wirkt: frisch, aktiv, stale, blockiert oder wartet auf Maintainer-Input.
blocked
KlarheitWie klar das Issue die erwartete Änderung, Akzeptanzkriterien und den nächsten Schritt erklärt.
clear
Voraussetzungen
GitHub Actionsshell scriptingcherry pick concepts
EinsteigerfreundlichkeitEin Score von 1 bis 100, der schätzt, wie zugänglich dieses Issue für First-Time Contributors ist.
50
Research-Richtung
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.