ENH: Added 4 Major Issue Templates #749
Merged
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
imikejackson
requested changes
Oct 24, 2023
nyoungbq
force-pushed
the
enh/issue_templates
branch
from
cfa2237 to
2170120
Compare
….yml, and 1 more file
nyoungbq
force-pushed
the
enh/issue_templates
branch
from
2170120 to
6af13d3
Compare
imikejackson
approved these changes
Oct 25, 2023
imikejackson
pushed a commit
to imikejackson/simplnx
that referenced
this pull request
Oct 20, 2024
One for bugs - bug_report.yml One for documentation additions or discrepancies - documentation_report.yml One for new features or enhancements - functionality_report.yml One for performance issues - performance_report.yml
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.
These mainly focus on stuff related specifically to complex since we have DREAM3DNX-Issues for most of the more casual GUI users that is found directly through the documentation. The exception to this rule is the bug report since someone may stumble upon this repository with less technical expertise and the main way for interacting with our library is NX GUI. I also opted to leave out the Security report since the default is better than anything I could put together to be honest.
In the future we can set up bots to automatically update these files with new releases and recent commit hashes to save updating them every time and boost usability for the reporter.
One for bugs - bug_report.yml
One for documentation additions or discrepancies - documentation_report.yml
One for new features or enhancements - functionality_report.yml
One for performance issues - performance_report.yml