-
Notifications
You must be signed in to change notification settings - Fork 18
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
Using GitHub discussions #128
Comments
I think that is pretty neat, but AFAICT there isn't a way to enable it in our repos at this time while it is in beta with only selected groups by GitHub. |
Ahh, hehe, seems like you are right 👍
|
I like the idea of actions that generally improves usage understanding as well as describes how a piece of code works. Given the technical problem with the above approach, how about improving the documentation of multer, that cover the specific aspects that you mentioned ? such as integration, architecture etc.? In addition, I would also like to see if we have a section that illustrates a complete life cycle events involved in a file upload operation - that might reduce a good amount of user issues in the repo IMO! |
I was told that I can get it enabled on ours if we want. That said, if you take a look at them in the npm RFCs repo, I am not sure it is great yet. They converted many issues to discussions, and some are hard to follow now. Also, I am not sure how the engagement has looked, we could ask @darcyclarke? |
GitHub Discussions is available on all public repositories now. |
We are already using GitHub Discussions :), well, in most of the repositories, where it has been needed. |
A lot of the issues we get on Multer is really people that want's help with doing specific setups, or integrating with another framework. The issue tracker isn't really the right place to discuss that, but maybe we could turn on GitHub Discussions and use that as a knowledge base for how to integrate/architect/etc?
I was recommended this by my friend @albinekb, who recommended looking at these two great examples:
ping @expressjs/triagers
The text was updated successfully, but these errors were encountered: