Add issue templates for bug reports and feature requests #323
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
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.
What do these changes do?
This pull request adds issue templates for the repository. Specifically, it introduces three templates:
bug_report.md): To help users report bugs with detailed information.feature_request.md): To guide users in requesting new features or enhancements.custom.md): For users to report issues that don't fit into the other categories.These templates will standardize how issues are reported and improve the maintainers' ability to triage and address them efficiently.
Are there changes in behavior for the user?
Yes, users will now be prompted to select an issue template when they create a new issue. This ensures that all relevant information is provided upfront, making the issue reporting process more structured and efficient.
Related issue number
This PR addresses issue #108.
Checklist