feat: remove needs-triage label when any triage label is added

[elizabeth-dev]

This change will make prow remove the label needs-triage when any triage/ label is added to an issue or PR. This is done via modifying the regex used to decide when to remove such label so that it accepts anything with the triage/ prefix and not just triage/accepted

Fixes kubernetes-sigs/prow#344

[k8s-ci-robot]

Welcome @elizabeth-dev!

It looks like this is your first PR to kubernetes/test-infra 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/test-infra has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @elizabeth-dev. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[BenTheElder]

/ok-to-test
/lgtm
/approve
/hold
Thank you!!
cc @kubernetes/sig-contributor-experience-leads

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: BenTheElder, elizabeth-dev

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• config/OWNERS [BenTheElder]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[BenTheElder]

Labels: https://github.com/kubernetes/kubernetes/labels?q=triage%2F
/triage accepted, /triage duplicate, /triage unresolved, /triage needs-information, /triage not-reproducible
should all work and remove needs-triage after this merges

[Priyankasaggu11929]

/triage accepted, /triage duplicate, /triage unresolved, /triage needs-information, /triage not-reproducible
should all work and remove needs-triage after this merges

Thanks @elizabeth-dev @BenTheElder. Even I assumed that this was already the case.

+1 (ContribEx)

[BenTheElder]

/hold cancel

[k8s-ci-robot]

@elizabeth-dev: Updated the plugins configmap in namespace default at cluster test-infra-trusted using the following files:

• key plugins.yaml using file config/prow/plugins.yaml

In response to this:

This change will make prow remove the label needs-triage when any triage/ label is added to an issue or PR. This is done via modifying the regex used to decide when to remove such label so that it accepts anything with the triage/ prefix and not just triage/accepted

Fixes kubernetes-sigs/prow#344

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.

[BenTheElder]

Confirmed working as intended with /triage needs-information :-)

Thank you!