Should we have a bot to manage issues?!
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 9.8k
- Forks
- 1.9k
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 41
Description
Hi @kdavisk6, @vitalijr2
Should we run a bot to close stale issues?
https://github.com/OpenFeign/querydsl/blob/master/.github/workflows/stale.yml
In general I don't have the time to help with issues, I try to focus on helping those that are helping too.
So, not sure if that would be helpful or not.
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
Start by reviewing the linked .github/workflows/stale.yml example and the repository's existing issue-management practices. Clarify the desired stale-issue policy, exemptions, timing, and maintainer approval before identifying a concrete implementation scope; done means an agreed workflow and documented behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100