MAINT: update new issues template to point to discussions forum #2292
+15
−11
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rowanc1
approved these changes
Jan 9, 2025
agoose77
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds a link to the Jupyter Book discussion forum for "new issue" templates.
I also propose that we update our "bug report" issue to just be a general bug report, not something "specific" to Jupyter Book 2. However we should make clear in the issue template that users should specify if this relates to JB 1 or 2.
This way, the new issue button menu should look like this:
Over time, if people are still opening unhelpful blank issues and not using the forum, then we can consider removing that option so only maintainers can open blank issues.