-
Notifications
You must be signed in to change notification settings - Fork 199
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
Docs and issue templates: clarify usage of issues and discussions #5527
Conversation
Co-authored-by: Edoardo Zoni <[email protected]>
Co-authored-by: Edoardo Zoni <[email protected]>
Co-authored-by: Edoardo Zoni <[email protected]>
Co-authored-by: Edoardo Zoni <[email protected]>
Co-authored-by: Edoardo Zoni <[email protected]>
What do you think of these changes? For context, the idea came up after realizing that the default blank issues (now unavailable) were being a bit overused/misused. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great, very nice guidance!
Adding a few links just to make it easier.
Ah sheesh, I just remembered you can add actual links (e.g., to discussions page) instead of using a template. @aeriforme @EZoni check out how homebrew does this: https://github.com/Homebrew/homebrew-core/issues/new/choose That way, we can still keep the blank issue option at the very end and add guidance when someone clicks new issue. |
This PR adds guidance and best practices on how to use issues and discussions.
This is useful to avoid issues that should be discussions, for example.