Modify issue template to keep unwanted issues out
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 13.6k
- Forks
- 2.6k
- PR merge metrics
- No merged PRs in 30d
Description
There seems to be a lot password cracking requests lately which acts like a positive feedback loop - those are indexed and new people are directed to john repository (which also means we should be removing rather than closing).
I've seen other github repositories use issue templates to provide steps how to file a bug, we could do the same to inform people that password cracking requests will be rejected.
I believe this is the procedure to do that:
https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository
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 with the GitHub issue-template configuration guide linked in the issue and inspect the repository's current issue-template configuration. Add guidance that password-cracking requests are rejected, then verify that the new-issue flow explains how to file a useful bug report and discourages those requests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 63/100