Configures the stale bot to manage inactive issues and PRs.#3834
Configures the stale bot to manage inactive issues and PRs.#3834meteorcloudy wants to merge 4 commits intobazelbuild:mainfrom
Conversation
meteorcloudy
changed the title
| Thank you for contributing to the rules_rust repository! | ||
| This issue has been marked as stale since it has not had any activity in the last 1+ years. It will be closed in the next 90 | ||
| days unless any other activity occurs. If you think this issue is still relevant and should stay open, please post any comment here and the issue will no longer be marked as stale. | ||
| close-issue-message: > |
There was a problem hiding this comment.
I originally added the stalebot to rules_python and then later deleted it
https://github.com/bazel-contrib/rules_python/commits/main/.github/workflows/stale.yml.
IMO it's great for us to have a bot label issues as stale, but a human should close them.
The reason we removed it is, when a real issue with the repo isn't being fixed, closing it simply reduces the accuracy of the data - a real issue exists but is no longer documented. It also discourages contributors who experience "well I took the time to report this and no one cares".
It's even worse for PRs.
There was a problem hiding this comment.
I think it depends on whether the project maintainers are actually triaging issues/PRs.
Assuming they are, then:
- If the issue / PR is unclear and waiting for more information from the reporter/contributor, the stale bot will close them if there is no activity.
- If a real issue exists, then the project maintainers should acknowledge that by adding the
not stalelabel or a priority label.
If there is no one looking at the issues/PRs at all, then nothing will meaningfully help.
2 participants
No description provided.