Make use of cherry-pick + format-patch to generate the patches, and in
particular, use the -x flag to produce a paper trail of how these
commits were selected. This makes it easy to look at a backported commit
and see where it came from and what PR it was associated with.

graphql feels extremely unpleasant to work with. But this info is
available there, and never has been for the REST api (why???) as
evidenced by the reliance on a crude hack, namely scanning events for a
commit reference "in the right vicinity".

And github stopped generating those reference events at all, so...

Hmm, not sure how this used to work.

These can be really slow.

More likely to resolve conflicts, leaves conflict markers which is
easier to inspect and fix / commit.