Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Idea: Labels to indicate whether automated backport is possible #132

Open
silverwind opened this issue Jul 13, 2024 · 0 comments
Open

Idea: Labels to indicate whether automated backport is possible #132

silverwind opened this issue Jul 13, 2024 · 0 comments

Comments

@silverwind
Copy link
Collaborator

silverwind commented Jul 13, 2024 •
edited
Loading

I'm often not sure whether a PR is cherry-pickable without conflict or not. It would be useful to have two new labels to indicate the cherry-pick-ability:

  • automated-backport-possible
  • automated-backport-impossible

These labels have no version so would only check against latest release branch.
@silverwind silverwind changed the title Idea: A label to indicate where automated backport is possible or not Idea: A label to indicate whether automated backport is possible or not Jul 13, 2024
@silverwind silverwind changed the title Idea: A label to indicate whether automated backport is possible or not Idea: Labels to indicate whether automated backport is possible Jul 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@silverwind