Test-infra: Question: Is there an OWNERS vs collaborators audit tool
Prow looks at both a repos collaborators and those in the OWNERS file to determine ownership. Is there any tool that would let one audit a repo and diff who is in the OWNERS files vs who is a collaborator to look for any gaps? For example, to find someone listed in an OWNERS file who is not a collaborator.
mattfarina
All 31 comments
I'm not aware of one. It probably shouldn't be very difficult to do using the GitHub APIs though. You might want to bring this up with sig-contribex.
BenTheElder
on 26 Oct 2017
Sounds like a useful tool to have. I think OWNERS are required to be collaborators but as people move between jobs/companies/projects, OWNERS can get stale.
kargakis
on 26 Oct 2017
The tools filter the OWNERS against the collaborators for, I believe, security purposes. Being able to do an audit would be useful for catching problems.
mattfarina
on 27 Oct 2017
cc @php-coder
kargakis
on 4 Dec 2017
/area prow
kargakis
on 4 Dec 2017
FYI, I've written one. With a little cleanup and some tests I'll PR it to the test-infra repo.
mattfarina
on 15 Dec 2017
/assign @mattfarina
stevekuznetsov
on 15 Dec 2017
any update on this?
spiffxp
on 5 Jan 2018
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
fejta-bot
on 5 Apr 2018
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale
fejta-bot
on 5 May 2018
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close
fejta-bot
on 4 Jun 2018
/remove-lifecycle rotten
/reopen
kargakis
on 4 Jun 2018
@kargakis: you can't re-open an issue/PR unless you authored it or you are assigned to it.
In response to this:
/remove-lifecycle rotten
/reopen
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.
k8s-ci-robot
on 4 Jun 2018
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
fejta-bot
on 2 Sep 2018
The linked PR has been aged out. I asked the author if they were going to pick it back up and they said it didn't seem like anyone wanted it. Is there any reason for this issue to remain open @kargakis ?
spiffxp
on 5 Sep 2018
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
fejta-bot
on 5 Oct 2018
This would be nice, especially if we could get it automated in verify-owners or similar, so users get better feedback on why their OWNERS isn't working.
/remove-lifecycle rotten
stevekuznetsov
on 7 Oct 2018
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
fejta-bot
on 5 Jan 2019
/remove-lifecycle stale
idealhack
on 5 Jan 2019
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
fejta-bot
on 5 Apr 2019
/remove-lifecycle stale
On Fri, Apr 5, 2019 at 3:58 PM fejta-bot notifications@github.com wrote:
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually
close.If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta
https://github.com/fejta.
/lifecycle stale—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/test-infra/issues/5175#issuecomment-480227153,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APXA0Id3yb3FcDawkK45O_h9BTaPVR5hks5vdyVlgaJpZM4QGtkD
.
nikhita
on 5 Apr 2019
Created https://github.com/kubernetes/test-infra/pull/12297 to update the verify-owners plugin to ensure that all new users added to OWNERS and OWNERS_ALIASES files are org collaborators.
I'm happy to follow up on the original WIP PR https://github.com/kubernetes/test-infra/pull/6165, but wanted to double check if we still want to have this? I think it could be useful to audit old OWNERS files...but I'm not sure if this should live in test-infra or if this should be a one off tool?
cc @cblecker
nikhita
on 21 Apr 2019
/sig contributor-experience
nikhita
on 21 Apr 2019
/cc @mrbobbytables ^^
nikhita
on 24 Apr 2019
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
fejta-bot
on 23 Jul 2019
ref: https://github.com/kubernetes/community/issues/1808 since this is about auditing OWNERS files, and that's the umbrella issue I keep linking to as I find related issues
spiffxp
on 24 Jul 2019
/remove-lifecycle stale
nikhita
on 22 Aug 2019
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
fejta-bot
on 20 Nov 2019
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
fejta-bot
on 20 Dec 2019
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close
fejta-bot
on 19 Jan 2020
@fejta-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue with/reopen.
Mark the issue as fresh with/remove-lifecycle rotten.Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close
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.
k8s-ci-robot
on 19 Jan 2020
Related issues
Aisuko
·
3Comments
zacharysarah
·
3Comments
cblecker
·
4Comments
spiffxp
·
3Comments
spzala
·
4Comments
Most helpful comment
FYI, I've written one. With a little cleanup and some tests I'll PR it to the test-infra repo.