yashdev9274 / yashdev9274/supercli
Issue and PR templates — bug reports, feature requests, PRs
Open
Beginner friendly
Nobody has claimed this yet.
infrastructure
repo core
- Dominant language
- TypeScript
- Stars
- 214
- Forks
- 41
- Avg merge
- 2h 26m
- Merged PRs (30d)
- 34
Description
Description
Create GitHub issue and PR templates for the repository.
Expected Deliverables
.github/ISSUE_TEMPLATE/bug-report.yml: version, OS, Node, provider, repro steps, expected vs actual, logs.github/ISSUE_TEMPLATE/feature-request.yml: problem, solution, alternatives.github/PULL_REQUEST_TEMPLATE.md: description, related issue, checklist (tested, linted, type-checked)config.ymlfor template chooser
Why
Consistent templates reduce back-and-forth and help contributors submit high-quality reports.
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
Create .github/ISSUE_TEMPLATE/bug-report.yml, .github/ISSUE_TEMPLATE/feature-request.yml, .github/PULL_REQUEST_TEMPLATE.md, and the template chooser config.yml. Start by checking the repository's existing GitHub configuration and validate the YAML structure in GitHub's template settings. Done means bug reports, feature requests, and pull requests present the requested fields and checklist to contributors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, typescript
- Domain
- developer-experience, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 74/100