WordPress/gutenberg

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

Open

#76,579 建立於 2026年3月17日

在 GitHub 查看
 (6 留言) (0 反應) (2 負責人)JavaScript (9,607 star) (3,893 fork)batch import
Good First Issue[Status] In Progress[Type] Build Tooling[Type] Enhancement

描述

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.

貢獻者指南

技術棧
javascriptgithub actions
領域
releaseci cd
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-2 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
blocked
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
GitHub Actionsshell scriptingcherry pick concepts
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
50
研究方向
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.