lincc-frameworks / lincc-frameworks/python-project-template
General issue is the same as Github's built-in blank issue?
Open
Nobody has claimed this yet.
- Dominant language
- Jinja
- Stars
- 85
- Forks
- 16
- Avg merge
- 6h 18m
- Merged PRs (30d)
- 1
Description
PPT provides three GitHub issue templates, but GitHub itself adds "Blank issue" to that list, which is basically the same as our "General issue." Should we remove "General issue" so the issue reporter is not confused?
Contributor guide
No contributing guide indexed for this repository
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 three GitHub issue templates and compare the existing “General issue” with GitHub’s built-in “Blank issue,” using the linked screenshot for context. Confirm whether they are functionally redundant, then update the template set so the issue reporter is not presented with duplicate choices.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100