-
Notifications
You must be signed in to change notification settings - Fork 10k
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
Use bot to remove stage/triaged tag if no activity for a while #19587
Comments
@siyuanfoundation |
/assign @IAMRogerXi Thank you! |
i will start the work on this item this week... |
PR: #19716 |
Hi, @IAMRogerXi. Thanks for your pull request. I see that you're introducing a new GitHub action. Because we have access to K8s' infra, and because we're trying to minimize our GirHub actions workflows, may I ask if you explored using the k8s-triage-bot as suggested in the description (https://github.com/kubernetes/test-infra/blob/9c8103abd65925a9e075c01908d40c31d00c1bbf/config%2Fjobs%2Fkubernetes%2Fsig-k8s-infra%2Ftrusted%2Fsig-contribex-k8s-triage-robot.yaml)? If it wasn't a good fit, can you explain why? Thanks, again! :) |
thanks for the comment. however, it is not that easy to setup a Prow command env to test the Prow commands like /remove-stage triaged in my own repository. may i know what will be a proper unit testing for this part? thanks. |
It is pretty hard to test it because of bot access limitations. We will have to depend on code review and see what happens ^_^. |
thanks for the explanation. i will abandon #19716 and push a new one with prow command in comment. |
i don't have time to push a PR last weekend. will try my best to do so this week... |
What would you like to be added?
Use a bot to remove stage/triaged tag if no activity in a PR/issue for a while (2 month?)
We can probably use the k8 triage bot
Why is this needed?
It is easier to rely on the
stage/triaged
tag filter to triage issues and PRs, but we need to watch out for abandoned issue/PR./cc @ivanvc @ArkaSaha30
The text was updated successfully, but these errors were encountered: