-
Notifications
You must be signed in to change notification settings - Fork 161
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-cleanup inactive members #3632
Comments
I did this manually - see the gist linked here: knative/community#1244 |
/label "help wanted" Can somebody add "help wanted" label to this ticket please? So that it shows up in https://clotributor.dev/search?project=knative |
Hi @aliok 👋 This is Sergio, one of the CLOTributor's maintainers. At the moment CLOTributor's feeds from the CLOMonitor's data files, and it only processes repositories listed there. There are a few Knative repositories listed on CLOMonitor, but this one doesn't seem to be there yet. You can submit a PR anytime to include more repositories if you'd like 🙂 |
Thanks @tegioz I will bring this up to Knative's Steering Committee to see what other repositories we can add. Thanks for the heads-up! |
This issue is stale because it has been open for 90 days with no |
Going to re-open this - I don't see the machinery in place to prune our peribolos configs https://github.com/knative/community/blob/main/peribolos/knative.yaml /lifecycle frozen |
/transfer knative/infra |
We have a huge list of team members that we can purge (ie. no interaction with any of the repos in the last two years) -- Dave from TOC
Would be nice to have this automated with maybe a courtesy email sent to the members that they would be removed.
The text was updated successfully, but these errors were encountered: