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

[senior-dev-bot[bot]]

Hi there! :wave: Thanks for opening a PR. :tada: To get the most out of Senior Dev, please sign up in our Web App, connect your GitHub account, and add/join your organization GuilhermeStracini. After that, you will receive code reviews beginning on your next opened PR. :rocket:

[korbit-ai[bot]]

My review is in progress :book: - I will have feedback for you in a few minutes!

[pr-code-reviewer[bot]]

:wave: Hi there!

1. Include a field for steps to reproduce the bug.
2. Ensure that there's a way to categorize the severity of the bug.
3. Validate user inputs such as file uploads or image attachments to aid in bug identification.

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

[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.

---

[!NOTE]

Summarized by CodeRabbit Free

Your organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting .

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 .` - `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 show all the console.log statements in this repository.` - `@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 as 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. Additionally, you can add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. ### 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.

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

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

1. .github/ISSUE_TEMPLATE/bug_report.yml:

   • The attribute required for the field screenshots is set to false, which contradicts the placeholder text implying it is optional. This could confuse users.
   • In the os field, providing instructions for multiple operating systems in the description might overwhelm users. Consider simplifying the guidance.
   • The title prefix "Bug: " is hardcoded in the template. This inflexibility may not align with the organization's naming conventions for issue titles.

2. .github/ISSUE_TEMPLATE/feature_request.yml:

   • The attachments field is marked as not required but the description suggests adding screenshots or diagrams. It's inconsistent and might lead to missing important context.
   • The proposed_solution field doesn't have a placeholder for users to see a default entry, unlike other fields that offer examples or placeholders. Adding a placeholder could guide users on the expected input format.
   • The description under problem and current_solution prompts for examples but lacks them in the placeholder. Providing placeholder examples could aid users in providing relevant information.

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

1. .github/ISSUE_TEMPLATE/bug_report.yml:

   • Consider allowing users to provide multiple attachments or supporting files by enhancing the template with a field for attachments to better capture and diagnose bugs efficiently.
   • Add a section or way to categorize the bug report (e.g., severity level, affected component) to provide a more structured and informative bug report.

2. .github/ISSUE_TEMPLATE/feature_request.yml:

   • Standardize the usage of placeholders in all fields to guide users consistently. Include examples wherever possible to assist users in filling out the template effectively.
   • Encourage users to elaborate on the impact of the problem by adding a field dedicated to describing the potential consequences or benefits of implementing the feature request.

[gooroo-dev[bot]]

Please double-check what I found in the pull request:

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

Summary of Proposed Changes

• ➕ Added a bug report issue template with detailed fields for bug behavior, logs, screenshots, steps to reproduce, expected behavior, possible cause, device, OS, browser, and additional information.
• ➕ Added a feature request issue template with fields for problem description, current solution, proposed solution, attachments, and additional information.

Identified Issues

No issues were identified in the proposed changes.

General Review

The proposed changes introduce two new issue templates for bug reports and feature requests. The templates are well-structured and include detailed fields to capture necessary information. The code quality and style are good, with no apparent issues. The templates should help streamline the process of reporting bugs and requesting features, making it easier for maintainers to gather relevant information.

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