Can we please stop "forcing" developers to create PRs for anything "non-critical"?

Open

#3,491 opened on Jan 9, 2026 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 5/5
Estimated time: Over a week
Newbie friendliness: 25/100

Issue type: Feature
Clarity: Needs clarification
Activity status: Stale
Tech stack: github
Domain: developer-experience

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.

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?

Dominant language: TypeScript
Stars: 2.6k
Forks: 1.5k
Avg merge: 2d 12h
Merged PRs (30d): 8

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.

Similar issues

[MagmaFusion] rapports qualité - contenus des rubriques en anglais manquants Open

Difficulty 2/5 1-3 hours Newbie friendliness 65/100

InseeFr/Bauhaus#1634 · Opened Sep 23, 2026
[Bug]: SSH host picker duplicates configured aliases and known_hosts targets Open

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

pingdotgg/t3code#13270 · Opened Sep 23, 2026
resetSseResponseWait and noteRequestProgress silently fail to re-arm the 60s relay timeout if progress tokens arrive as strings Open

bug v2

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

modelcontextprotocol/inspector#2458 · 1 comment · Opened Sep 23, 2026
Resources: Update work of changsha Open

Difficulty 1/5 Under an hour Newbie friendliness 75/100

railmapgen/rmp-gallery#4068 · Opened Sep 23, 2026
sass-1.105.0.tgz: 1 vulnerabilities (highest severity is: 7.5) Open

Mend: dependency security vulnerability status: needs triage 🕵️‍♀️

Difficulty 2/5 1-3 hours Newbie friendliness 70/100

carbon-design-system/ibm-products#9907 · Opened Sep 23, 2026

More TypeScript issues