Please remove "Stale" bot
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
Is your feature request related to a problem? Please describe
The fact that so many important bug reports and feature requests have been closed by the Stale bot is frustrating.
Users spend a significant amount of time writing feature requests and bug reports.
The Stale bot required me to follow Github notifications carefully to determine when an issue was tagged as stale, then go to that issue, and request that the meta: never-stale label be added, since closing an issue that has not yet been resolved will serve no purpose.
Describe the behaviour you'd like
As I understand it, Stale bot is used to get rid of any issues that are no longer of importance.
In my personal experience, I have never submitted issues that I did not believe were significant.
I wish a human would keep track of the issues that should be closed, assuming all issues are relevant.
There should be a known outcome for any issue submitted by a Gitpod user.
(Please feel free to describe real outcomes, I will just provide a few examples)
- Duplicate issue (we have already addressed it elsewhere)
- Unable to replicate the problem (we need more information/data/examples to find a solution)
- Solved (🎉)
- Out of scope (The feature is not within the scope of the project)
Describe alternatives you've considered
Additional context
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 GitHub Stale bot configuration and the issue discussion. The requested outcome is to remove the bot and ensure issues receive a human-reviewed outcome rather than automatic closure; the payload does not identify repository files, tests, or an implementation entry point.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 20/100