Add 2 issue templates

[gitauto-ai[bot]]

Overview

This PR adds issue templates to the repository so that you can create issues more easily for GitAuto and your project. Please review the changes and merge the PR if you agree.

Added templates:

• bug_report.yml
• feature_request.yml

[korbit-ai[bot]]

By default, I don't review pull requests opened by bots. If you would like me to review this pull request anyway, you can request a review via the /korbit-review command in a comment.

[semanticdiff-com[bot]]

Review changes with SemanticDiff.

[senior-dev-bot[bot]]

Hi there! :wave: Thanks for opening a PR. It looks like you've already reached the 5 review limit on our Basic Plan for the week. If you still want a review, feel free to upgrade your subscription in the Web App and then reopen the PR

[pr-code-reviewer[bot]]

:wave: Hi there!

1. Consider adding clearer instructions and guidelines for users filling out the bug report.
2. Ensure all necessary information fields are present to facilitate efficient bug identification and resolution.
3. Validate input data to prevent submission errors and enhance the quality of bug reports.

_{^{Automatically generated with the help of gpt-3.5-turbo. Feedback? Please don't hesitate to drop me an email at webber@takken.io.}}

[instapr[bot]]

Comment

Great work on adding the bug_report.yml and feature_request.yml templates! The templates look comprehensive and well-structured. Thank you for enhancing the repository with these helpful additions. Please proceed with merging the PR once the review is complete.

[codara-ai-code-review[bot]]

Potential issues, bugs, and flaws that can introduce unwanted behavior:

1. /.github/ISSUE_TEMPLATE/bug_report.yml
   • The screenshots field is set as not required (false), but to improve issue clarity, it may be beneficial to make it required or clarify its optional nature with users to encourage providing relevant visuals.

Code suggestions and improvements for better exception handling, logic, standardization, and consistency:

1. /.github/ISSUE_TEMPLATE/bug_report.yml
   • Consider adding more specific validation rules to fields (e.g., max length for text fields) to improve data quality and consistency.
   • Ensure consistent terminology across fields (e.g., "Logs" vs. "Screenshots or Diagrams") for a better user understanding.
   • Implement a more structured error handling mechanism to gracefully manage validation errors or missing data when users submit the form.
2. /.github/ISSUE_TEMPLATE/feature_request.yml
   • Similar to the bug report template, make a consistent decision on whether to require attachments (like screenshots or diagrams) to provide a comprehensive feature request.
   • Apply specific character limits or formats for text fields where applicable to guide users in providing concise and focused information.
   • Establish a standardized error messaging system to support users in completing mandatory fields they might have missed, ensuring a smoother submission process.

[coderabbitai[bot]]

[!IMPORTANT]

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Tips

### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: -- `I pushed a fix in commit , please review it.` -- `Generate unit testing code for this file.` - `Open a follow-up GitHub issue for this discussion.` - Files and specific lines of code (under the "Files changed" tab): Tag `@coderabbitai` in a new review comment at the desired location with your query. Examples: -- `@coderabbitai generate unit testing code for this file.` -- `@coderabbitai modularize this function.` - PR comments: Tag `@coderabbitai` in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples: -- `@coderabbitai generate interesting stats about this repository and render them as a table.` -- `@coderabbitai read src/utils.ts and generate unit testing code.` -- `@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.` -- `@coderabbitai help me debug CodeRabbit configuration file.` Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. ### CodeRabbit Commands (Invoked using PR comments) - `@coderabbitai pause` to pause the reviews on a PR. - `@coderabbitai resume` to resume the paused reviews. - `@coderabbitai review` to trigger an incremental review. This is useful when automatic reviews are disabled for the repository. - `@coderabbitai full review` to do a full review from scratch and review all the files again. - `@coderabbitai summary` to regenerate the summary of the PR. - `@coderabbitai resolve` resolve all the CodeRabbit review comments. - `@coderabbitai configuration` to show the current CodeRabbit configuration for the repository. - `@coderabbitai help` to get help. ### Other keywords and placeholders - Add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. - Add `@coderabbitai summary` to generate the high-level summary at a specific location in the PR description. - Add `@coderabbitai` anywhere in the PR title to generate the title automatically. ### CodeRabbit Configuration File (`.coderabbit.yaml`) - You can programmatically configure CodeRabbit by adding a `.coderabbit.yaml` file to the root of your repository. - Please see the [configuration documentation](https://docs.coderabbit.ai/guides/configure-coderabbit) for more information. - If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: `# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json` ### Documentation and Community - Visit our [Documentation](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](https://discord.com/invite/GsXnASn26c) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.

[gooroo-dev[bot]]

Please double check the following review of the pull request:

Issues counts

🐞Mistake	🤪Typo	🚨Security	🚀Performance	💪Best Practices	📖Readability	❓Others
0	0	0	0	1	0	0

Changes in the diff

• ➕ Added a bug report issue template.
• ➕ Added a feature request issue template.

Identified Issues

ID	Type	Details	Severity	Confidence
1	💪Best Practices	The value attribute in steps_to_reproduce is unnecessary and should be removed.	🟡Low	🟡Low

Issue 1

Type: 💪Best Practices
Details: The value attribute in steps_to_reproduce is unnecessary and should be removed.
File Path: .github/ISSUE_TEMPLATE/bug_report.yml
Lines: 52-54

Explanation

The value attribute is set to "1." which is redundant and may confuse users. Removing it will make the template cleaner and more user-friendly.

Code Fix

diff --git a/.github/ISSUE_TEMPLATE/bug_report.yml b/.github/ISSUE_TEMPLATE/bug_report.yml
index e8123b1..0000000 100644
--- a/.github/ISSUE_TEMPLATE/bug_report.yml
+++ b/.github/ISSUE_TEMPLATE/bug_report.yml
@@ -51,7 +51,6 @@ body:
       placeholder: |
         Example: 
         1. Go to "Upload"
         2. Click on "Select File"
         3. Choose a large file (over 100MB)
         4. Click "Upload"
         5. See error
-      value: |
-        1. 
     validations:
       required: true

Explanation of the Fix

The fix removes the unnecessary value attribute from the steps_to_reproduce section, making the template cleaner.

Missing Tests

Since the changes involve adding issue templates, there are no traditional code tests to be added. However, it is recommended to manually test the templates by creating dummy issues using the new templates to ensure they work as expected.

Summon me to re-review when updated! Yours, Gooroo.dev React or reply to share your thoughts!

[github-actions[bot]]

Infisical secrets check: :white_check_mark: No secrets leaked!

Scan results:

10:53AM INF scanning for exposed secrets...
10:53AM INF 5 commits scanned.
10:53AM INF scan completed in 66ms
10:53AM INF no leaks found