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.

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

Feature Request: exclusive label sets #179

Open
jberkus opened this issue May 31, 2024 · 3 comments
Open

Feature Request: exclusive label sets #179

jberkus opened this issue May 31, 2024 · 3 comments
Assignees
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. sig/contributor-experience Categorizes an issue or PR as relevant to SIG Contributor Experience. sig/release Categorizes an issue or PR as relevant to SIG Release.

Comments

@jberkus
Copy link

jberkus commented May 31, 2024

This was originally this issue, opened at the request of the release team.

Currently, it's entirely possible to assign an issue or a PR multiple "priority" or multiple "lifecycle" labels. This doesn't make any sense; a given issue/PR can only have one priority, or one lifecycle stage. The Release Team and Enhancements both end up spending time cleaning up these "duplicates".

It would be really nice if we were able to create "exclusive sets" of labels, where adding a label from the set would automatically cause any other label in the set to be removed. These sets would include:

  • priority/
  • lifecycle/
  • tracked/

This feature request has been a TODO for 5 years because it will require rewriting some/all of the label handler.

/kind feature
/sig contributor-experience
/sig release
/priority important-longterm
/help-wanted

@k8s-ci-robot k8s-ci-robot added kind/feature Categorizes issue or PR as related to a new feature. sig/contributor-experience Categorizes an issue or PR as relevant to SIG Contributor Experience. sig/release Categorizes an issue or PR as relevant to SIG Release. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. labels May 31, 2024
@jberkus
Copy link
Author

jberkus commented May 31, 2024

/help

@k8s-ci-robot
Copy link
Contributor

@jberkus:
This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

  • Why are we solving this issue?
  • To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
  • Does this issue have zero to low barrier of entry?
  • How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

/help

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@k8s-ci-robot k8s-ci-robot added the help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. label May 31, 2024
@amirrmonfared
Copy link
Contributor

I would like to take part in this issue, but it may take a bit of time and I would be more than happy if someone wants to help :D
/assign

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. sig/contributor-experience Categorizes an issue or PR as relevant to SIG Contributor Experience. sig/release Categorizes an issue or PR as relevant to SIG Release.
Projects
None yet
Development

No branches or pull requests

3 participants