-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
Auto label PRs on Github #17970
Comments
Agree this would be great to start bringing online. Thanks @liangyuanpeng for drafting the initial pr to enable it in For this to be helpful we do need to add nested Nested |
/assign @liangyuanpeng |
@jmhbnz: GitHub didn't allow me to assign the following users: liangyuanpeng. Note that only etcd-io members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. In response to this:
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. |
Hi @jmhbnz , as far as I know, |
Yes. But we need to work carefully and set up the nested |
Very nice feature to have let me know if i can help with anything. |
/assign |
What would you like to be added?
Would be nice for PR discovery to have them automatically labeled based on directory they touch.
For example if the test touches
./tests/robustness
we can always label it witharea/robustness-testing
.I think K8s OWNERS support this https://go.k8s.io/owners
cc @jmhbnz
Why is this needed?
Better discovery of PRs for people interested in reviewing robustness test changes.
The text was updated successfully, but these errors were encountered: