Document the cherry-picking automation

[adamziel]

What?

Documents the cherry-picking automation introduced in PR 40969.

CC @gziolo @ryanwelcher @ockham

[ockham]

Thanks a lot for documenting this! Looks good; I had one minor nitpick (scattered across multiple comments 😅)

[gziolo]

Thank you so much for adding this document. I left my feedback on how we could improve the clarity of when this tool can be used. Anyway, I didn't see any blockers, and we can iterate on that.

[gziolo]

This document is also linked from the section that covers cherry-picking bugs for the Gutenberg plugin releases. As far as I know, we don't have a label for plugin releases, so we should create one as part of the process.

It would also be helpful to make it clear at the top of the document that, by default, it works with the current major WordPress release. Alternatively, we could add the logic that detects the label based on the name of the branch:

• release/X.Y - plugin release
• wp/X.Y - WP release

[adamziel]

There's nothing major WP release specific in here – it works for the current git branch. I'll clarify that further.

[adamziel]

The autodetection logic would be really nice, too! I'll leave it as a TODO note for anyone who wishes to pick that up

[gziolo]

I think the confusion would get resolved with autodetection of the label that should be scanned.

Anyway, it's fine to leave a note with some examples how to approach that based on the scenario.

[gziolo]

Excellent revisions ❤️