fabricbot should close issues with no activity as not planned, not as fixed
Open
enhancement
- Dominant language
- Bicep
- Stars
- 3.6k
- Forks
- 830
- Avg merge
- 1d 21m
- Merged PRs (30d)
- 79
Description
This issue has no description.
Contributor guide
Research direction
The issue body names no files, tests, or configuration entry points. Start by locating the repository's Fabricbot configuration and reviewing how inactive issues are closed; done means the configured closure reason is “not planned” rather than “fixed,” with any relevant automation check passing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100