chore: add issue templates for bug reports and feature requests

[NEXARA-oss]

Problem

The repository currently lacks structured GitHub issue templates.

This results in inconsistent bug reports and unclear feature requests.

---

Goal

Add contributor-friendly GitHub issue templates.

---

Tasks

• create bug report template
• create feature request template
• create documentation issue template
• improve issue creation guidance

---

Acceptance Criteria

• templates appear during issue creation
• required fields are clear
• issue formatting becomes standardized

---

[riyapetle]

Hi! I'm a GSSoC'26 contributor and I'd like to work on this issue.

My approach:

• Create a .github/ISSUE_TEMPLATE/ directory to host the new YAML-based configuration files.
• Bug Report: Implement fields for "Steps to Reproduce," "Expected vs Actual Behavior," and "Environment Details" (OS, Browser, etc.).
• Feature Request: Design a flow focusing on the "Problem Statement," "Proposed Solution," and "Alternative Considered."
• Documentation Issue: Create a streamlined template to identify missing or outdated docs with a field for suggested improvements.
• Issue Guidance: Configure a config.yml to set up a "Blank Issue" fallback and provide a clear "Contact Support" or "Security Policy" link.

I will be working with the GitHub Issue Forms (YAML syntax) rather than basic Markdown to provide a more structured and interactive user experience (input fields, checkboxes, and dropdowns). I'll ensure each template includes appropriate default labels to automate issue categorization.

ETA: 1 day. Please assign this to me!

[NEXARA-oss]

Thanks for your interest in contributing 🚀

The project admin application for GSSoC is currently under review. Once confirmation is finalized, I’ll begin assigning issues and coordinating contributions properly. Meanwhile, feel free to explore the repository and the open issues.

[divyanshivermaa]

Hi! I'm a GSSoC 2026 contributor and would love to work on this issue. Please assign it to me.

[NEXARA-oss]

Hey @riyapetle 👋

Really liked the structured approach proposed for improving the repository issue workflow, especially around YAML issue forms, contributor guidance, automated categorization, and standardized reporting.

This aligns very well with PulseStack’s contributor onboarding and repository management goals 🚀

Assigning this issue to you.
Feel free to share progress updates or draft template previews during development.

[NEXARA-oss]

@riyapetle please drop an implementation plan so that we could confirm your working on this issue !

[riyapetle]

Hii @NEXARA-oss , this is the implementation plan

Implementation Plan: Add GitHub Issue Templates

1. Create GitHub Issue Template Structure

Add a .github/ISSUE_TEMPLATE/ directory in the repository.

Recommended structure:

.github/
└── ISSUE_TEMPLATE/
    ├── bug_report.yml
    ├── feature_request.yml
    ├── documentation_issue.yml
    └── config.yml

---

2. Create Bug Report Template

File

/.github/ISSUE_TEMPLATE/bug_report.yml

Purpose

Standardize bug submissions and ensure contributors provide reproducible details.

Fields to Include

• bug summary

• expected behavior

• actual behavior

• steps to reproduce

• screenshots/logs

• environment details

  • OS
  • browser/version
  • app version

• additional context

Validation

Mark important fields as required:

• summary
• reproduction steps
• expected behavior

---

3. Create Feature Request Template

File

/.github/ISSUE_TEMPLATE/feature_request.yml

Purpose

Encourage clear and actionable feature proposals.

Fields to Include

• problem statement
• proposed solution
• alternatives considered
• use case
• additional context/mockups

Validation

Required fields:

• problem statement
• proposed solution
• use case

---

4. Create Documentation Issue Template

File

/.github/ISSUE_TEMPLATE/documentation_issue.yml

Purpose

Help contributors report missing, outdated, or unclear documentation.

Fields to Include

• documentation location/page
• issue description
• suggested improvement
• screenshots/examples (optional)

Validation

Required fields:

• affected documentation
• issue description

---

5. Improve Issue Creation Guidance

File

/.github/ISSUE_TEMPLATE/config.yml

Tasks

• disable blank issues if desired
• add helpful contact/support links
• guide contributors toward discussions for questions

Example Improvements

• link to contribution guidelines
• link to README/setup docs
• message encouraging template usage

---

6. Verify Template Functionality

Testing Steps

• push templates to a test branch
• open “New Issue” on GitHub
• confirm all templates appear correctly
• verify required fields enforce input
• ensure markdown formatting renders properly

---

7. Review for Contributor Experience

Final Checks

• wording is beginner-friendly
• forms are concise but informative
• labels/emojis/categories are consistent
• no unnecessary required fields

---

Expected Outcome

After implementation:

• contributors see structured issue options
• issue quality becomes more consistent
• maintainers receive actionable reports
• triaging and prioritization become easier
• repository contribution workflow improves

[NEXARA-oss]

looks good