Skip to content

Don't Put Conflicting Backport Labels on PRΒ #282

@dsanders11

Description

@dsanders11

If trop gets confused due to a bug or humans applying labels, PRs can end up with both backport/accepted βœ… and backport/requested πŸ—³ on it. We should prevent these conflicting labels, and also prevent trop from modifying backport labels on a merged backport PR.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions