-
Notifications
You must be signed in to change notification settings - Fork 137
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate Issue to discussion in nodejs/help
#771
Comments
nodejs/help
/cc @nodejs/tsc |
@AugustinMauroy could you update the "docs" links to be in "English"? |
@ovflowd Done! |
Is there an existing tool to do it? |
GitHub itself allows to convert issues as discussions, but not sure if in bull. Need to investigate. But pretty sure there might be 3rd party tool that does that. |
You can click on a button to pass an issue in discussion. But since there are 600 issues I think that searching or developing a tool would be smarter. |
This is a little bit in conflict with #679. I think it could be confusing to have two user/help-related discussion forums. |
For me it is necessary to have the discussion org for collaborative work and feedback. And the discution help for the discussion between our community |
I mean, https://github.com/nodejs/node/discussions is already used for help discussions, not for org collaboration. |
This comment was marked as spam.
This comment was marked as spam.
FWIW there is a proposal to complete disable From a triage perspective, I am +1, as discussions have categories, answerability, and more that is useful for support-requests ( |
Migrate Issue to discussion in nodejs/help
I propose to migrate the issues on the nodejs/help repo to discussion.
The major advantage is the "mark as solved" feature. It allows you to put a comment as a solution. And it is displayed below the question.
The sections in the dissection allow to organize the types of help.
There is also a way to make templates like in the issues.
The sections that could be set up:
Ref:
Docs GitHub about discussion
Docs Github about issue
The text was updated successfully, but these errors were encountered: