Skip to content

PR incorrectly classifed as still needing backports (w/ labels) #23

Open
Open
PR incorrectly classifed as still needing backports (w/ labels)#23

Description

@StanFromIreland
StanFromIreland
opened on Jul 3, 2026

The troublesome PR: python/cpython#150179

Backports were merged, but the labels remained. However it was still reported as needing backports instead of just needing the labels to be removed (as of July 3).

Activity

  1. hugovk commented on Jul 3, 2026

    @hugovk
    hugovk
    on Jul 3, 2026
    Owner

    The text under the "PRs missing backports" header reads:

    These PRs have a "needs backport to 3.x" label but no backport PR. Create a manual backport if there was a conflict, or remove the label if the backport is no longer needed.

    That covers this?

    "PRs missing backports or labels removed" is a little long for a header.

  2. StanFromIreland commented on Jul 3, 2026

    @StanFromIreland
    StanFromIreland
    on Jul 3, 2026
    ContributorAuthor

    Sorry, the bug I'm thinking about is it not being under "PRs with backports." But it doesn’t really matter, feel free to close.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions