Hi David, +1 – an automated labelling would help. The baseRefName attribute could be requested from the GraphQL query [1], allowing to add/remove a “backport” label accordingly. Do you already have an idea of the labelling, such as “Backport_<target_branch>”?
[1] https://github.com/apache/flink/blob/master/.github/workflows/community-review.sh#L46 Regards, Sebastien Pereira On 13/08/2025, 17:32, "David Radley" <[email protected]> wrote: Hello, I have been reviewing PRs and notice that some titles of PRs in crude [BP-…] to indicate that the PR is a back port. Other PRs just have the same title, and it is not obvious as a reviewer whether the PR is a back port or a duplicate. I was thinking that a label for non master targeted PRs to indicate the version would help make back port PRs more obvious. I am happy to implement this if the community agrees; this could be done pretty easily in the existing community review github action, WDYT? Kind regards, David. Unless otherwise stated above: IBM United Kingdom Limited Registered in England and Wales with number 741598 Registered office: Building C, IBM Hursley Office, Hursley Park Road, Winchester, Hampshire SO21 2JN Unless otherwise stated above: Compagnie IBM France Siège Social : 17, avenue de l'Europe, 92275 Bois-Colombes Cedex RCS Nanterre 552 118 465 Forme Sociale : S.A.S. Capital Social : 664 614 175,50 € SIRET : 552 118 465 03644 - Code NAF 6203Z
