Skip to content

Conversation

@aduh95
Copy link
Contributor

@aduh95 aduh95 commented Jan 24, 2026

The discussion in #61487 made me realize we lack a statement saying "you don't need to open an issue, actually we'd prefer if you open a PR directly if you already know what you want". In fact, we were kinda hinting the opposite, which does not reflect the reality of the issue tracker in my experience, resulting in frustrating experience for both reporters and triagers.

@nodejs-github-bot
Copy link
Collaborator

Review requested:

  • @nodejs/tsc

@nodejs-github-bot nodejs-github-bot added the doc Issues and PRs related to the documentations. label Jan 24, 2026
Comment on lines +4 to +5
It is usually more productive to first send the Pull Request implementing the
feature, even imperfectly, and let the discussion happen during code review.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What if the implemented feature is what you really don't want to, which will end up with great-pains-but-all-in-vain?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

doc Issues and PRs related to the documentations.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants