Implement stalebot
Open
Nobody has claimed this yet.
question
- Dominant language
- Python
- Stars
- 8.3k
- Forks
- 835
- Avg merge
- 5d 3h
- Merged PRs (30d)
- 1
Description
Might be worth us implementing stalebot - we are getting towards 100 issue open now, and stalebot will trim down the list by checking if the issues are abandoned or not.
Let me know you thoughts @ericwb and would this fit in with the PyCQA plan of things @sigmavirus24 ?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the linked stalebot GitHub App and the repository's current issue-management process first; no implementation files or tests are named. Define the configuration needed to identify abandoned issues and the review/closure behavior, then verify it can reduce the open-issue list without closing active work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100