Skip to content

Feature Request: Do not apply Still Needs Manual Backport label to backport PR #93

Closed
@pllim

Description

Workflow to trigger this:

  1. Have two different backport labels applied, so when merged, a PR would be backported to two different release branches.
  2. One of the release branch will have a failed backport, triggering the bot to apply "Still Needs Manual Backport".

Current behavior: If the failed backport happened first, the original PR will have "Still Needs Manual Backport" label applied. And then the backport to the other branch that succeeds after will also inherit this label.

Desired behavior: Bot is smart enough to not let the second backport to inherit this label.

Maybe not everyone will agree on this request, therefore I am opening an issue instead of attempting to patch it.

Example: astropy/astropy#14104

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions