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

Why this is a good first issue

Automating manual cherry-pick detection requires GitHub Actions expertise.

AI Summary

The issue addresses the problem of missing labels on original PRs after manual cherry-picks, proposing automation to detect and label them correctly. The solution involves GitHub Actions and may require specific PR content, but linking closed PRs is uncertain.

Issue 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.

GitHub Labels

[Type] EnhancementGood First Issue[Status] In Progress[Type] Build Tooling