Add 2 issue templates

[gitauto-ai]

Why is this feature needed?

To streamline issue submission, we are introducing two new issue templates for Bug Reports and Feature Requests. These templates help contributors provide all the necessary information in a structured manner, ensuring that we can diagnose and address issues or consider feature improvements efficiently.

What and how are we changing? Why this approach?

Two YAML template files have been added under the .github/ISSUE_TEMPLATE directory:

• bug_report.yml: This template guides users to include detailed information such as bug behavior, logs, reproduction steps, expected behavior, and additional context.
• feature_request.yml: This template ensures users describe the problem, explain their current workaround, propose a desired solution, and share any attachments that could clarify their request.

Using YAML to define these templates provides a consistent, dynamic, and easily maintainable way to collect issue-specific data, which improves the overall quality and triage speed of submitted issues.

What actions are required from users?

• Users should now select the appropriate issue template (Bug Report or Feature Request) when submitting an issue.
• They need to follow the provided guidelines in each template to ensure all critical information is included.

How does it work? (Technical details)

• The bug_report.yml template includes fields such as bug behavior, logs, screenshots, steps to reproduce, and more, with each field carrying validations (e.g., required fields) to ensure completeness.
• The feature_request.yml template collects necessary data on the problem, current solution, proposed solution, and any helpful attachments.
• GitHub automatically detects YAML templates in the .github/ISSUE_TEMPLATE directory, enabling these options as soon as a new issue is created.

Is it backwards compatible?

Yes, adding these issue templates is fully backwards compatible. Existing issues and workflows will remain unaffected. These templates will simply augment the process for new issue submissions.

Any other considerations?

• Future improvements could include refining the validations or adding more templates to serve additional use cases.
• We considered allowing optional fields for more flexibility; however, the current approach ensures a baseline level of detail, which is critical for effective issue resolution.
• Feedback from contributors on the usability of these templates is welcome, so we can iterate and improve them over time.

[gitauto-ai]

Why is this feature needed?

To streamline issue submission, we are introducing two new issue templates for Bug Reports and Feature Requests. These templates help contributors provide all the necessary information in a structured manner, ensuring that we can diagnose and address issues or consider feature improvements efficiently.

What and how are we changing? Why this approach?

Two YAML template files have been added under the .github/ISSUE_TEMPLATE directory:

• bug_report.yml: This template guides users to include detailed information such as bug behavior, logs, reproduction steps, expected behavior, and additional context.
• feature_request.yml: This template ensures users describe the problem, explain their current workaround, propose a desired solution, and share any attachments that could clarify their request.

Using YAML to define these templates provides a consistent, dynamic, and easily maintainable way to collect issue-specific data, which improves the overall quality and triage speed of submitted issues.

What actions are required from users?

• Users should now select the appropriate issue template (Bug Report or Feature Request) when submitting an issue.
• They need to follow the provided guidelines in each template to ensure all critical information is included.

How does it work? (Technical details)

• The bug_report.yml template includes fields such as bug behavior, logs, screenshots, steps to reproduce, and more, with each field carrying validations (e.g., required fields) to ensure completeness.
• The feature_request.yml template collects necessary data on the problem, current solution, proposed solution, and any helpful attachments.
• GitHub automatically detects YAML templates in the .github/ISSUE_TEMPLATE directory, enabling these options as soon as a new issue is created.

Is it backwards compatible?

Yes, adding these issue templates is fully backwards compatible. Existing issues and workflows will remain unaffected. These templates will simply augment the process for new issue submissions.

Any other considerations?

• Future improvements could include refining the validations or adding more templates to serve additional use cases.
• We considered allowing optional fields for more flexibility; however, the current approach ensures a baseline level of detail, which is critical for effective issue resolution.
• Feedback from contributors on the usability of these templates is welcome, so we can iterate and improve them over time.

[gitauto-ai]

Why is this feature needed?

To streamline issue submission, we are introducing two new issue templates for Bug Reports and Feature Requests. These templates help contributors provide all the necessary information in a structured manner, ensuring that we can diagnose and address issues or consider feature improvements efficiently.

What and how are we changing? Why this approach?

Two YAML template files have been added under the .github/ISSUE_TEMPLATE directory:

• bug_report.yml: This template guides users to include detailed information such as bug behavior, logs, reproduction steps, expected behavior, and additional context.
• feature_request.yml: This template ensures users describe the problem, explain their current workaround, propose a desired solution, and share any attachments that could clarify their request.

Using YAML to define these templates provides a consistent, dynamic, and easily maintainable way to collect issue-specific data, which improves the overall quality and triage speed of submitted issues.

What actions are required from users?

• Users should now select the appropriate issue template (Bug Report or Feature Request) when submitting an issue.
• They need to follow the provided guidelines in each template to ensure all critical information is included.

How does it work? (Technical details)

• The bug_report.yml template includes fields such as bug behavior, logs, screenshots, steps to reproduce, and more, with each field carrying validations (e.g., required fields) to ensure completeness.
• The feature_request.yml template collects necessary data on the problem, current solution, proposed solution, and any helpful attachments.
• GitHub automatically detects YAML templates in the .github/ISSUE_TEMPLATE directory, enabling these options as soon as a new issue is created.

Is it backwards compatible?

Yes, adding these issue templates is fully backwards compatible. Existing issues and workflows will remain unaffected. These templates will simply augment the process for new issue submissions.

Any other considerations?

• Future improvements could include refining the validations or adding more templates to serve additional use cases.
• We considered allowing optional fields for more flexibility; however, the current approach ensures a baseline level of detail, which is critical for effective issue resolution.
• Feedback from contributors on the usability of these templates is welcome, so we can iterate and improve them over time.

[gitauto-ai]

Why is this feature needed?

To streamline issue submission, we are introducing two new issue templates for Bug Reports and Feature Requests. These templates help contributors provide all the necessary information in a structured manner, ensuring that we can diagnose and address issues or consider feature improvements efficiently.

What and how are we changing? Why this approach?

Two YAML template files have been added under the .github/ISSUE_TEMPLATE directory:

• bug_report.yml: This template guides users to include detailed information such as bug behavior, logs, reproduction steps, expected behavior, and additional context.
• feature_request.yml: This template ensures users describe the problem, explain their current workaround, propose a desired solution, and share any attachments that could clarify their request.

Using YAML to define these templates provides a consistent, dynamic, and easily maintainable way to collect issue-specific data, which improves the overall quality and triage speed of submitted issues.

What actions are required from users?

• Users should now select the appropriate issue template (Bug Report or Feature Request) when submitting an issue.
• They need to follow the provided guidelines in each template to ensure all critical information is included.

How does it work? (Technical details)

• The bug_report.yml template includes fields such as bug behavior, logs, screenshots, steps to reproduce, and more, with each field carrying validations (e.g., required fields) to ensure completeness.
• The feature_request.yml template collects necessary data on the problem, current solution, proposed solution, and any helpful attachments.
• GitHub automatically detects YAML templates in the .github/ISSUE_TEMPLATE directory, enabling these options as soon as a new issue is created.

Is it backwards compatible?

Yes, adding these issue templates is fully backwards compatible. Existing issues and workflows will remain unaffected. These templates will simply augment the process for new issue submissions.

Any other considerations?

• Future improvements could include refining the validations or adding more templates to serve additional use cases.
• We considered allowing optional fields for more flexibility; however, the current approach ensures a baseline level of detail, which is critical for effective issue resolution.
• Feedback from contributors on the usability of these templates is welcome, so we can iterate and improve them over time.

[gitauto-ai]

Why is this feature needed?

To streamline issue submission, we are introducing two new issue templates for Bug Reports and Feature Requests. These templates help contributors provide all the necessary information in a structured manner, ensuring that we can diagnose and address issues or consider feature improvements efficiently.

What and how are we changing? Why this approach?

Two YAML template files have been added under the .github/ISSUE_TEMPLATE directory:

• bug_report.yml: This template guides users to include detailed information such as bug behavior, logs, reproduction steps, expected behavior, and additional context.
• feature_request.yml: This template ensures users describe the problem, explain their current workaround, propose a desired solution, and share any attachments that could clarify their request.

Using YAML to define these templates provides a consistent, dynamic, and easily maintainable way to collect issue-specific data, which improves the overall quality and triage speed of submitted issues.

What actions are required from users?

• Users should now select the appropriate issue template (Bug Report or Feature Request) when submitting an issue.
• They need to follow the provided guidelines in each template to ensure all critical information is included.

How does it work? (Technical details)

• The bug_report.yml template includes fields such as bug behavior, logs, screenshots, steps to reproduce, and more, with each field carrying validations (e.g., required fields) to ensure completeness.
• The feature_request.yml template collects necessary data on the problem, current solution, proposed solution, and any helpful attachments.
• GitHub automatically detects YAML templates in the .github/ISSUE_TEMPLATE directory, enabling these options as soon as a new issue is created.

Is it backwards compatible?

Yes, adding these issue templates is fully backwards compatible. Existing issues and workflows will remain unaffected. These templates will simply augment the process for new issue submissions.

Any other considerations?

• Future improvements could include refining the validations or adding more templates to serve additional use cases.
• We considered allowing optional fields for more flexibility; however, the current approach ensures a baseline level of detail, which is critical for effective issue resolution.
• Feedback from contributors on the usability of these templates is welcome, so we can iterate and improve them over time.

[gitauto-ai]

Why is this feature needed?

To streamline issue submission, we are introducing two new issue templates for Bug Reports and Feature Requests. These templates help contributors provide all the necessary information in a structured manner, ensuring that we can diagnose and address issues or consider feature improvements efficiently.

What and how are we changing? Why this approach?

Two YAML template files have been added under the .github/ISSUE_TEMPLATE directory:

• bug_report.yml: This template guides users to include detailed information such as bug behavior, logs, reproduction steps, expected behavior, and additional context.
• feature_request.yml: This template ensures users describe the problem, explain their current workaround, propose a desired solution, and share any attachments that could clarify their request.

Using YAML to define these templates provides a consistent, dynamic, and easily maintainable way to collect issue-specific data, which improves the overall quality and triage speed of submitted issues.

What actions are required from users?

• Users should now select the appropriate issue template (Bug Report or Feature Request) when submitting an issue.
• They need to follow the provided guidelines in each template to ensure all critical information is included.

How does it work? (Technical details)

• The bug_report.yml template includes fields such as bug behavior, logs, screenshots, steps to reproduce, and more, with each field carrying validations (e.g., required fields) to ensure completeness.
• The feature_request.yml template collects necessary data on the problem, current solution, proposed solution, and any helpful attachments.
• GitHub automatically detects YAML templates in the .github/ISSUE_TEMPLATE directory, enabling these options as soon as a new issue is created.

Is it backwards compatible?

Yes, adding these issue templates is fully backwards compatible. Existing issues and workflows will remain unaffected. These templates will simply augment the process for new issue submissions.

Any other considerations?

• Future improvements could include refining the validations or adding more templates to serve additional use cases.
• We considered allowing optional fields for more flexibility; however, the current approach ensures a baseline level of detail, which is critical for effective issue resolution.
• Feedback from contributors on the usability of these templates is welcome, so we can iterate and improve them over time.

[gitauto-ai]

Why is this feature needed?

To streamline issue submission, we are introducing two new issue templates for Bug Reports and Feature Requests. These templates help contributors provide all the necessary information in a structured manner, ensuring that we can diagnose and address issues or consider feature improvements efficiently.

What and how are we changing? Why this approach?

Two YAML template files have been added under the .github/ISSUE_TEMPLATE directory:

• bug_report.yml: This template guides users to include detailed information such as bug behavior, logs, reproduction steps, expected behavior, and additional context.
• feature_request.yml: This template ensures users describe the problem, explain their current workaround, propose a desired solution, and share any attachments that could clarify their request.

Using YAML to define these templates provides a consistent, dynamic, and easily maintainable way to collect issue-specific data, which improves the overall quality and triage speed of submitted issues.

What actions are required from users?

• Users should now select the appropriate issue template (Bug Report or Feature Request) when submitting an issue.
• They need to follow the provided guidelines in each template to ensure all critical information is included.

How does it work? (Technical details)

• The bug_report.yml template includes fields such as bug behavior, logs, screenshots, steps to reproduce, and more, with each field carrying validations (e.g., required fields) to ensure completeness.
• The feature_request.yml template collects necessary data on the problem, current solution, proposed solution, and any helpful attachments.
• GitHub automatically detects YAML templates in the .github/ISSUE_TEMPLATE directory, enabling these options as soon as a new issue is created.

Is it backwards compatible?

Yes, adding these issue templates is fully backwards compatible. Existing issues and workflows will remain unaffected. These templates will simply augment the process for new issue submissions.

Any other considerations?

• Future improvements could include refining the validations or adding more templates to serve additional use cases.
• We considered allowing optional fields for more flexibility; however, the current approach ensures a baseline level of detail, which is critical for effective issue resolution.
• Feedback from contributors on the usability of these templates is welcome, so we can iterate and improve them over time.

[gitauto-ai]

Why is this feature needed?

To streamline issue submission, we are introducing two new issue templates for Bug Reports and Feature Requests. These templates help contributors provide all the necessary information in a structured manner, ensuring that we can diagnose and address issues or consider feature improvements efficiently.

What and how are we changing? Why this approach?

Two YAML template files have been added under the .github/ISSUE_TEMPLATE directory:

• bug_report.yml: This template guides users to include detailed information such as bug behavior, logs, reproduction steps, expected behavior, and additional context.
• feature_request.yml: This template ensures users describe the problem, explain their current workaround, propose a desired solution, and share any attachments that could clarify their request.

Using YAML to define these templates provides a consistent, dynamic, and easily maintainable way to collect issue-specific data, which improves the overall quality and triage speed of submitted issues.

What actions are required from users?

• Users should now select the appropriate issue template (Bug Report or Feature Request) when submitting an issue.
• They need to follow the provided guidelines in each template to ensure all critical information is included.

How does it work? (Technical details)

• The bug_report.yml template includes fields such as bug behavior, logs, screenshots, steps to reproduce, and more, with each field carrying validations (e.g., required fields) to ensure completeness.
• The feature_request.yml template collects necessary data on the problem, current solution, proposed solution, and any helpful attachments.
• GitHub automatically detects YAML templates in the .github/ISSUE_TEMPLATE directory, enabling these options as soon as a new issue is created.

Is it backwards compatible?

Yes, adding these issue templates is fully backwards compatible. Existing issues and workflows will remain unaffected. These templates will simply augment the process for new issue submissions.

Any other considerations?

• Future improvements could include refining the validations or adding more templates to serve additional use cases.
• We considered allowing optional fields for more flexibility; however, the current approach ensures a baseline level of detail, which is critical for effective issue resolution.
• Feedback from contributors on the usability of these templates is welcome, so we can iterate and improve them over time.