Consistent stalebot rules
Open
:sparkles: kaizen
- Dominant language
- No language data
- Stars
- 3.4k
- Forks
- 679
- PR merge metrics
- No merged PRs in 30d
Description
We have some really ancient PRs and Issues in some repos, e.g. https://github.com/cucumber/cucumber-cpp/pull/129
I'd like to use Stalebot to help us manage this, and I think it would be good to try and have a consistent rule set for all our repos.
Contributor guide
Research direction
Start by reviewing the linked cucumber-cpp pull request #129 and the Stalebot requirements implied by this issue. Identify the repositories and rule variations that need consideration, then define a consistent rule set and confirm that Stalebot can apply it across the repositories.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100