microsoft / microsoft/TypeScript-Website
Can we please stop "forcing" developers to create PRs for anything "non-critical"?
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.6k
- Forks
- 1.5k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 7
Description
I get it, you want help and most issues can be fixed easily with a small PR, but this feels wrong and if someone wants to create a small issue to report a small problem without expecting it to be solved anytime soon because he understand that there are many genuinely critical problems to worry about by the maintainers, the way it's worded is as if you were doing something wrong for reporting it.
Maybe consider adding an option to report "non-critical" issues to at least give us the option while also warning us that they will take way longer to be fixed than the critical ones and to consider contributing?
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
The issue names no repository files, tests, or entry points. Start by reviewing the reporting workflow shown in the attached image and clarify the desired behavior for non-critical reports; done would require an agreed design and an identified implementation path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100