Add 2 issue templates

[gitauto-for-dev]

Why is this feature needed?

To streamline how users report bugs and request new features, we've added two issue templates. These templates help gather consistent and comprehensive information by providing structured forms. This is important for improving issue triaging and ensuring that developers have all the necessary details upfront.

What and how are we changing? Why this approach?

We've added two new YAML files in the .github/ISSUE_TEMPLATE directory:

• bug_report.yml: Contains a detailed template for bug reports, including fields for bug behavior, logs, screenshots, reproduction steps, expected behavior, and system details.
• feature_request.yml: Contains a detailed template for feature requests, including fields for the problem description, current workaround, proposed solution, and additional information.

This approach standardizes the issue submission process, making it easier to diagnose problems and understand feature needs quickly. The structured format ensures that contributors provide crucial context, which speeds up turnaround times for fixes and improvements.

What actions are required from users?

Users can now select the appropriate issue template (Bug Report or Feature Request) when opening a new issue on GitHub. No additional configuration is required on the user’s part; simply choose the provided template that best matches your issue.

How does it work? (Technical details)

• The bug_report.yml template defines multiple form fields of types such as textarea and input. Each field comes with attributes like labels, descriptions, placeholders, and validations to ensure required information is provided.
• The feature_request.yml template follows a similar format, guiding users to fill in details about the problem, current solutions, and the propose changes.
• GitHub automatically recognizes .github/ISSUE_TEMPLATE and configures the new issue forms based on these YAML definitions.

Is it backwards compatible?

Yes, adding these templates does not affect any existing repository functionality. They are an enhancement to the issue submission process and are completely backward compatible.

Any other considerations?

• The template fields have been designed to prompt users for clear, actionable details, which should help maintain high-quality issue reports.
• We made sure to include validations for required fields to reduce incomplete issue submissions.
• Future improvements could include additional templates for other issue types if necessary, based on user feedback.

[gitauto-for-dev]

Why is this feature needed?

To streamline how users report bugs and request new features, we've added two issue templates. These templates help gather consistent and comprehensive information by providing structured forms. This is important for improving issue triaging and ensuring that developers have all the necessary details upfront.

What and how are we changing? Why this approach?

We've added two new YAML files in the .github/ISSUE_TEMPLATE directory:

• bug_report.yml: Contains a detailed template for bug reports, including fields for bug behavior, logs, screenshots, reproduction steps, expected behavior, and system details.
• feature_request.yml: Contains a detailed template for feature requests, including fields for the problem description, current workaround, proposed solution, and additional information.

This approach standardizes the issue submission process, making it easier to diagnose problems and understand feature needs quickly. The structured format ensures that contributors provide crucial context, which speeds up turnaround times for fixes and improvements.

What actions are required from users?

Users can now select the appropriate issue template (Bug Report or Feature Request) when opening a new issue on GitHub. No additional configuration is required on the user’s part; simply choose the provided template that best matches your issue.

How does it work? (Technical details)

• The bug_report.yml template defines multiple form fields of types such as textarea and input. Each field comes with attributes like labels, descriptions, placeholders, and validations to ensure required information is provided.
• The feature_request.yml template follows a similar format, guiding users to fill in details about the problem, current solutions, and the propose changes.
• GitHub automatically recognizes .github/ISSUE_TEMPLATE and configures the new issue forms based on these YAML definitions.

Is it backwards compatible?

Yes, adding these templates does not affect any existing repository functionality. They are an enhancement to the issue submission process and are completely backward compatible.

Any other considerations?

• The template fields have been designed to prompt users for clear, actionable details, which should help maintain high-quality issue reports.
• We made sure to include validations for required fields to reduce incomplete issue submissions.
• Future improvements could include additional templates for other issue types if necessary, based on user feedback.

[gitauto-for-dev]

Why is this feature needed?

To streamline how users report bugs and request new features, we've added two issue templates. These templates help gather consistent and comprehensive information by providing structured forms. This is important for improving issue triaging and ensuring that developers have all the necessary details upfront.

What and how are we changing? Why this approach?

We've added two new YAML files in the .github/ISSUE_TEMPLATE directory:

• bug_report.yml: Contains a detailed template for bug reports, including fields for bug behavior, logs, screenshots, reproduction steps, expected behavior, and system details.
• feature_request.yml: Contains a detailed template for feature requests, including fields for the problem description, current workaround, proposed solution, and additional information.

This approach standardizes the issue submission process, making it easier to diagnose problems and understand feature needs quickly. The structured format ensures that contributors provide crucial context, which speeds up turnaround times for fixes and improvements.

What actions are required from users?

Users can now select the appropriate issue template (Bug Report or Feature Request) when opening a new issue on GitHub. No additional configuration is required on the user’s part; simply choose the provided template that best matches your issue.

How does it work? (Technical details)

• The bug_report.yml template defines multiple form fields of types such as textarea and input. Each field comes with attributes like labels, descriptions, placeholders, and validations to ensure required information is provided.
• The feature_request.yml template follows a similar format, guiding users to fill in details about the problem, current solutions, and the propose changes.
• GitHub automatically recognizes .github/ISSUE_TEMPLATE and configures the new issue forms based on these YAML definitions.

Is it backwards compatible?

Yes, adding these templates does not affect any existing repository functionality. They are an enhancement to the issue submission process and are completely backward compatible.

Any other considerations?

• The template fields have been designed to prompt users for clear, actionable details, which should help maintain high-quality issue reports.
• We made sure to include validations for required fields to reduce incomplete issue submissions.
• Future improvements could include additional templates for other issue types if necessary, based on user feedback.

[gitauto-for-dev]

Why is this feature needed?

To streamline how users report bugs and request new features, we've added two issue templates. These templates help gather consistent and comprehensive information by providing structured forms. This is important for improving issue triaging and ensuring that developers have all the necessary details upfront.

What and how are we changing? Why this approach?

We've added two new YAML files in the .github/ISSUE_TEMPLATE directory:

• bug_report.yml: Contains a detailed template for bug reports, including fields for bug behavior, logs, screenshots, reproduction steps, expected behavior, and system details.
• feature_request.yml: Contains a detailed template for feature requests, including fields for the problem description, current workaround, proposed solution, and additional information.

This approach standardizes the issue submission process, making it easier to diagnose problems and understand feature needs quickly. The structured format ensures that contributors provide crucial context, which speeds up turnaround times for fixes and improvements.

What actions are required from users?

Users can now select the appropriate issue template (Bug Report or Feature Request) when opening a new issue on GitHub. No additional configuration is required on the user’s part; simply choose the provided template that best matches your issue.

How does it work? (Technical details)

• The bug_report.yml template defines multiple form fields of types such as textarea and input. Each field comes with attributes like labels, descriptions, placeholders, and validations to ensure required information is provided.
• The feature_request.yml template follows a similar format, guiding users to fill in details about the problem, current solutions, and the propose changes.
• GitHub automatically recognizes .github/ISSUE_TEMPLATE and configures the new issue forms based on these YAML definitions.

Is it backwards compatible?

Yes, adding these templates does not affect any existing repository functionality. They are an enhancement to the issue submission process and are completely backward compatible.

Any other considerations?

• The template fields have been designed to prompt users for clear, actionable details, which should help maintain high-quality issue reports.
• We made sure to include validations for required fields to reduce incomplete issue submissions.
• Future improvements could include additional templates for other issue types if necessary, based on user feedback.

[gitauto-for-dev]

Why is this feature needed?

To streamline how users report bugs and request new features, we've added two issue templates. These templates help gather consistent and comprehensive information by providing structured forms. This is important for improving issue triaging and ensuring that developers have all the necessary details upfront.

What and how are we changing? Why this approach?

We've added two new YAML files in the .github/ISSUE_TEMPLATE directory:

• bug_report.yml: Contains a detailed template for bug reports, including fields for bug behavior, logs, screenshots, reproduction steps, expected behavior, and system details.
• feature_request.yml: Contains a detailed template for feature requests, including fields for the problem description, current workaround, proposed solution, and additional information.

This approach standardizes the issue submission process, making it easier to diagnose problems and understand feature needs quickly. The structured format ensures that contributors provide crucial context, which speeds up turnaround times for fixes and improvements.

What actions are required from users?

Users can now select the appropriate issue template (Bug Report or Feature Request) when opening a new issue on GitHub. No additional configuration is required on the user’s part; simply choose the provided template that best matches your issue.

How does it work? (Technical details)

• The bug_report.yml template defines multiple form fields of types such as textarea and input. Each field comes with attributes like labels, descriptions, placeholders, and validations to ensure required information is provided.
• The feature_request.yml template follows a similar format, guiding users to fill in details about the problem, current solutions, and the propose changes.
• GitHub automatically recognizes .github/ISSUE_TEMPLATE and configures the new issue forms based on these YAML definitions.

Is it backwards compatible?

Yes, adding these templates does not affect any existing repository functionality. They are an enhancement to the issue submission process and are completely backward compatible.

Any other considerations?

• The template fields have been designed to prompt users for clear, actionable details, which should help maintain high-quality issue reports.
• We made sure to include validations for required fields to reduce incomplete issue submissions.
• Future improvements could include additional templates for other issue types if necessary, based on user feedback.

[gitauto-for-dev]

Why is this feature needed?

To streamline how users report bugs and request new features, we've added two issue templates. These templates help gather consistent and comprehensive information by providing structured forms. This is important for improving issue triaging and ensuring that developers have all the necessary details upfront.

What and how are we changing? Why this approach?

We've added two new YAML files in the .github/ISSUE_TEMPLATE directory:

• bug_report.yml: Contains a detailed template for bug reports, including fields for bug behavior, logs, screenshots, reproduction steps, expected behavior, and system details.
• feature_request.yml: Contains a detailed template for feature requests, including fields for the problem description, current workaround, proposed solution, and additional information.

This approach standardizes the issue submission process, making it easier to diagnose problems and understand feature needs quickly. The structured format ensures that contributors provide crucial context, which speeds up turnaround times for fixes and improvements.

What actions are required from users?

Users can now select the appropriate issue template (Bug Report or Feature Request) when opening a new issue on GitHub. No additional configuration is required on the user’s part; simply choose the provided template that best matches your issue.

How does it work? (Technical details)

• The bug_report.yml template defines multiple form fields of types such as textarea and input. Each field comes with attributes like labels, descriptions, placeholders, and validations to ensure required information is provided.
• The feature_request.yml template follows a similar format, guiding users to fill in details about the problem, current solutions, and the propose changes.
• GitHub automatically recognizes .github/ISSUE_TEMPLATE and configures the new issue forms based on these YAML definitions.

Is it backwards compatible?

Yes, adding these templates does not affect any existing repository functionality. They are an enhancement to the issue submission process and are completely backward compatible.

Any other considerations?

• The template fields have been designed to prompt users for clear, actionable details, which should help maintain high-quality issue reports.
• We made sure to include validations for required fields to reduce incomplete issue submissions.
• Future improvements could include additional templates for other issue types if necessary, based on user feedback.

[gitauto-for-dev]

Why is this feature needed?

To streamline how users report bugs and request new features, we've added two issue templates. These templates help gather consistent and comprehensive information by providing structured forms. This is important for improving issue triaging and ensuring that developers have all the necessary details upfront.

What and how are we changing? Why this approach?

We've added two new YAML files in the .github/ISSUE_TEMPLATE directory:

• bug_report.yml: Contains a detailed template for bug reports, including fields for bug behavior, logs, screenshots, reproduction steps, expected behavior, and system details.
• feature_request.yml: Contains a detailed template for feature requests, including fields for the problem description, current workaround, proposed solution, and additional information.

This approach standardizes the issue submission process, making it easier to diagnose problems and understand feature needs quickly. The structured format ensures that contributors provide crucial context, which speeds up turnaround times for fixes and improvements.

What actions are required from users?

Users can now select the appropriate issue template (Bug Report or Feature Request) when opening a new issue on GitHub. No additional configuration is required on the user’s part; simply choose the provided template that best matches your issue.

How does it work? (Technical details)

• The bug_report.yml template defines multiple form fields of types such as textarea and input. Each field comes with attributes like labels, descriptions, placeholders, and validations to ensure required information is provided.
• The feature_request.yml template follows a similar format, guiding users to fill in details about the problem, current solutions, and the propose changes.
• GitHub automatically recognizes .github/ISSUE_TEMPLATE and configures the new issue forms based on these YAML definitions.

Is it backwards compatible?

Yes, adding these templates does not affect any existing repository functionality. They are an enhancement to the issue submission process and are completely backward compatible.

Any other considerations?

• The template fields have been designed to prompt users for clear, actionable details, which should help maintain high-quality issue reports.
• We made sure to include validations for required fields to reduce incomplete issue submissions.
• Future improvements could include additional templates for other issue types if necessary, based on user feedback.

[gitauto-for-dev]

Why is this feature needed?

To streamline how users report bugs and request new features, we've added two issue templates. These templates help gather consistent and comprehensive information by providing structured forms. This is important for improving issue triaging and ensuring that developers have all the necessary details upfront.

What and how are we changing? Why this approach?

We've added two new YAML files in the .github/ISSUE_TEMPLATE directory:

• bug_report.yml: Contains a detailed template for bug reports, including fields for bug behavior, logs, screenshots, reproduction steps, expected behavior, and system details.
• feature_request.yml: Contains a detailed template for feature requests, including fields for the problem description, current workaround, proposed solution, and additional information.

This approach standardizes the issue submission process, making it easier to diagnose problems and understand feature needs quickly. The structured format ensures that contributors provide crucial context, which speeds up turnaround times for fixes and improvements.

What actions are required from users?

Users can now select the appropriate issue template (Bug Report or Feature Request) when opening a new issue on GitHub. No additional configuration is required on the user’s part; simply choose the provided template that best matches your issue.

How does it work? (Technical details)

• The bug_report.yml template defines multiple form fields of types such as textarea and input. Each field comes with attributes like labels, descriptions, placeholders, and validations to ensure required information is provided.
• The feature_request.yml template follows a similar format, guiding users to fill in details about the problem, current solutions, and the propose changes.
• GitHub automatically recognizes .github/ISSUE_TEMPLATE and configures the new issue forms based on these YAML definitions.

Is it backwards compatible?

Yes, adding these templates does not affect any existing repository functionality. They are an enhancement to the issue submission process and are completely backward compatible.

Any other considerations?

• The template fields have been designed to prompt users for clear, actionable details, which should help maintain high-quality issue reports.
• We made sure to include validations for required fields to reduce incomplete issue submissions.
• Future improvements could include additional templates for other issue types if necessary, based on user feedback.