goldbergyoni / goldbergyoni/nodebestpractices
Create a policy of permanently deleting empty issues
- Dominant language
- Dockerfile
- Stars
- 106k
- Forks
- 10.7k
- PR merge metrics
- No merged PRs in 30d
Description
One of the only reasons I can think of for creating empty issues is to cheat Hacktober events, or the like (that give rewards to people for creating issues and PRs for OSS). So by permanently deleting them, you ensure that those creating bots don't receive any benefit from opening empty issues here. To make sure we're not closing issues from people who are still just figuring it out, we could set some number of hours before it gets deleted.
It seems like something there should be a github bot for; I'll look into that.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no repository files, tests, or entry points. Start by investigating whether a GitHub bot can identify empty issues and apply a configurable waiting period before permanent deletion. Done means a documented, agreed policy and an implemented automation path, but the issue does not define the exact timing or mechanism.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100