Add stale-bot #816
Open
Add stale-bot #816
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
janhoy
commented
Jan 27, 2026
| # This workflow warns of PRs that have had no activity for a specified amount of time. | ||
| # | ||
| # For more information, see https://github.com/actions/stale | ||
| name: Mark stale pull requests |
Contributor
Author
There was a problem hiding this comment.
Suggested change
| name: Mark stale pull requests | |
| name: Mark stale pull requests and issues |
|
I like! It helps us understand what are active efforts and what are "one offs" that never move forward. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We have a pretty long list of open issues, stretching back to 2019. Some may still be valid and can be picked up for work. Other are just ideas that may have become obsolete.
This PR adds the same stale-bot as we use on the main solr repo. It's not intended to devalue bug reports, feature requests or PR contributions, but rather to help nudge / surface things and force an action. That action may be add more info, trigger a manual close or adding a label to protect against being marked stale (long term feature).
Rules for PRs are 60 days before stale and 60 more days before close.
Rules for issues are 180 days before stale and 60 more days before close.