Request: Tool to scan OWNERS files for sig labels #6288
Labels
area/community-management
area/devstats
Issues or PRs related to the devstats subproject
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
lifecycle/rotten
Denotes an issue or PR that has aged beyond stale and will be auto-closed.
sig/contributor-experience
Categorizes an issue or PR as relevant to SIG Contributor Experience.
Comments
k8s-ci-robot
added
sig/contributor-experience
|
/help |
|
@mrbobbytables: GuidelinesPlease ensure that the issue body includes answers to the following questions:
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 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/test-infra repository. |
k8s-ci-robot
added
the
help wanted
|
Hey @mrbobbytables I along with @daemon1024 are working on #5425 so maybe we can help get this issue done too. Just want some guide how exactly do you want it to be |
|
@AvineshTripathi sgtm! please feel free to self-assign. One thing - I would consider this a higher priority to complete than #5425 so that we can ensure devstats and sigs.yaml is up to date for the annual reports 👍 |
|
Hey @mrbobbytables I have tried something and on running I am getting the following output : here for each owner file in repo the code is giving labels list Plese tell if I am going in wrong direction also how I should proceed further P.S : above output is just small part of entire output |
|
Hey @mrbobbytables I have done converting it into csv here is what it looks like : -> I have done the manual checking and I feel the code does checks every |
|
@AvineshTripathi is the initial PoC implementation commited somewhere? Asking since I can try and give early feedback on the implementation side of things and see how it can be tested out :) |
|
Hey @MadhavJivrajani I have kept in my k/Community clone. Here is the link to the code (link) would be happy to get review from you and also ignore the spell 😄 |
|
Left a few comments here: AvineshTripathi@aa817fa |
|
Hey @MadhavJivrajani I am stuck at a place doing the changes you sugested can you look at it link |
|
I've been able to automate this... sample output: labels.csv looks like this: |
|
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
k8s-ci-robot
added
the
lifecycle/stale
|
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
k8s-ci-robot
added
lifecycle/rotten
|
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /close |
|
@k8s-triage-robot: Closing this issue. 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/test-infra repository. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A small script or program to scan a dir path for OWNERS files and report on any sig labels found within any ONWERS file it discovers.
This tool will serve 2 purposes:
/sig contributor-experience
/area devstats
/area community-management
The text was updated successfully, but these errors were encountered: