Original PRs may not be tagged properly when a manual cherry-pick is performed.
#76.579 aperta il 17 mar 2026
Metriche repository
- Star
- (9607 star)
- Metriche merge PR
- (Merge medio 12g 18h) (509 PR mergiate in 30 g)
Descrizione
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.