Add GitHub Issue Templates

[Vishvapatel2047]

Add GitHub Issue Templates

Problem

The repository currently does not provide GitHub Issue Templates. As a result, contributors may submit issues with inconsistent formatting, omit important information, or provide insufficient details for maintainers to effectively understand and triage the issue.

Proposed Solution

Create a new directory:

.github/ISSUE_TEMPLATE/

Add the following issue templates:

• Bug Report
• Feature Request
• Documentation Improvement (optional)

Each template should guide contributors to provide relevant information, including:

• Description

  • A clear and concise explanation of the issue or request.

• Current Behavior

  • Describe what is happening now.

• Expected Behavior

  • Describe what should happen instead.

• Steps to Reproduce (for bug reports)

  • Provide a list of steps that consistently reproduce the issue.

• Screenshots (if applicable)

  • Include screenshots or screen recordings to help illustrate the issue.

• Additional Context

  • Any extra information that may help maintainers understand or resolve the issue.

Benefits

• Encourages consistent and well-structured issue reports.
• Makes issue triaging faster and more efficient.
• Improves the contributor experience by providing clear guidance.
• Reduces back-and-forth communication during issue discussions.
• Helps maintainers gather all necessary information from the initial report.

[Vishvapatel2047]

@Mrinalray Please assign this issue to me under ECSOC'26!

[anishagrawal25]

Hi @Mrinalray,

I'd like to work on this issue.

I can create structured GitHub issue templates for bug reports and feature requests, ensuring contributors provide the necessary information for easier issue tracking and triaging.

Could you please assign this issue to me?

Thank you!

[Atharv094]

Hi maintainers! I’d love to work on this issue. I can set up the .github/ISSUE_TEMPLATE/ directory with structured Bug Report, Feature Request, and Documentation templates. Could you please assign this to me?

Also, is this issue under the ECSoC program? If it is, kindly add the "EcSoc26" label. Thanks!