Disable stale bot or extend period
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 40.4k
- Forks
- 8.1k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 96
Description
Description
My feature request got closed by the GitHub bot: https://github.com/php/php-src/issues/21324#event-31212229923
Even though I am still interested in this feature, it didn't let me enough time, 14 days in the busiest period of the year is clearly not enough.
Also this is an insult to the time we are taking, as contributors, to identify issues / missing features and creating reports.
I understand the need to identify issues that are not relevant anymore, but feature requests are always relevant. Even if it was just for issues, 14 days is way too short, we have lives, kids, works, and other more important stuff, we are not AI machines, please allow us more time or allow us to reopen issues…
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 issue and event to understand how the stale bot closed the feature request, then locate the repository's stale-bot configuration or policy. Done means the requested behavior is clearly decided and the bot is disabled, its period is extended, or reopening is supported as agreed.
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
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100