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.