Request: move bugs back to GitHub.com.


(Joe Pea) #1

My report over at version script is not failing when preversion script fails. so far has no replies. Seems like NPM devs aren’t paying attention to this forum as closely as they were the GitHub issue tracker.

Maybe bugs should be moved back to GitHub issues.


(Joe Pea) #2

Or, maybe because Discourse doesn’t have a tagging system and other features like GitHub does, it isn’t apparent that any action has been taken on that issue. For example on GitHub there the issue thread shows when an owner has added labels, etc.


(Joe Pea) #3

Separating bugs to GitHub and leaving npm.community for support and other community stuff might make things easier to manage?


(Kat Marchán) #4

I actually look at this forum every day. We won’t be moving bugs back to GitHub because they were unmanageable.

I missed your specific bug in my triage, and it’s been triaged now. We’ll address it when we can. I’ve also marked it as a good first bug for folks.


(Jehy) #5

Same here, my topic is completely ignored:


(Lars Willighagen) #6

Your topic was triaged, not completely ignored. Since it mentioned the PR you have already opened on GitHub, waiting for a review, there isn’t much else that can be done here AFAIK. Whether or not the additional (second) issue report is posted on here instead of on the main GitHub repo has little influence on the review process of the PR, which is still on GitHub, I think.


Why does npm use discourse rather than github issues like every other open source project in the world