https://github.com/kubernetes/kubernetes/issues/50048 and https://github.com/kubernetes/contrib/issues/2713 are issues about ensuring that every user in an OWNERS or OWNERS_ALIASES file is an org member or outside collaborator.
Rather than doing a manual scan occasionally, we could add this check to the verify-owners plugin and automate it.
If this sounds good, I can work on it.
/cc @cblecker @spiffxp @dims @cjwagner @BenTheElder
/sig contributor-experience
/area prow
/kind feature
I think it's a good idea! Thanks.
This would potentially open the door to abuse so we'd have to cap the number of people we check when someone commits an OWNERS file, but otherwise sounds reasonable.
Capping the number of people we check wouldn't really be a barrier to abuse. It is still possible to just repeatedly push new commits to keep triggering validation. This is true for most all of our automation unfortunately.
A cap would still be good to avoid using all our tokens if/when big OWNERS file refactors happen, though.
/assign
I couldn't get this working on a private repo, but wanted to test here just to make sure I'm not imagining this category for /pony...
/pony lgtm
In response to this:
I couldn't get this working on a private repo, but wanted to test here just to make sure I'm not imagining this category for
/pony.../pony lgtm
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/test-infra repository.
/pony approve
@spiffxp: Couldn't find a pony matching that query.
In response to this:
/pony approve
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/test-infra repository.
/pony sad
In response to this:
/pony sad
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/test-infra repository.
Just for the record - this was fixed in https://github.com/kubernetes/test-infra/pull/10741. :)
@spiffxp If you can explain the difference between an lgtm pony and an approval pony, I will make /pony approve work. ;)
Here too: https://github.com/kubernetes/test-infra/issues/8838#issuecomment-436075246 @tallclair
@nikhita are you working on that issue?
/reopen
This was reverted in https://github.com/kubernetes/test-infra/pull/12402.
Created https://github.com/kubernetes/test-infra/pull/12460 to fix it and add the feature again.
@nikhita: Reopened this issue.
In response to this:
/reopen
This was reverted in https://github.com/kubernetes/test-infra/pull/12402.
Created https://github.com/kubernetes/test-infra/pull/12460 to fix it and add the feature again.
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/test-infra repository.
Most helpful comment
@spiffxp If you can explain the difference between an lgtm pony and an approval pony, I will make
/pony approvework. ;)