Skip to content

Add standardized Github Issue Templates - #442

Closed
ayushsri-dev wants to merge 1 commit into
SATYAM-PRATIBHAN:mainfrom
ayushsri-dev:feat/issue-templates
Closed

Add standardized Github Issue Templates#442
ayushsri-dev wants to merge 1 commit into
SATYAM-PRATIBHAN:mainfrom
ayushsri-dev:feat/issue-templates

Conversation

@ayushsri-dev

Copy link
Copy Markdown

Description

This PR adds standardized GitHub Classic Markdown Issue Templates and supporting documentation to streamline issue reporting, maintainer triage, and GSSoC 2026 contributor assignment workflows across the repository.

Summary of Changes:

  1. GitHub Issue Templates (.github/ISSUE_TEMPLATE/):

    • bug_report.md — Structured bug reporting template with reproduction steps, error logs, and environment details.
    • feature_request.md — Feature proposal template with problem statement, technical details, and acceptance criteria.
    • documentation.md — Documentation improvement proposal template.
    • ui_ux_improvement.md — UI styling, responsiveness, dark mode, and accessibility enhancement template.
    • enhancement.md — Code refactoring, TypeScript typing, and DX tooling template.
  2. Issue Helper Config (.github/ISSUE_TEMPLATE/config.yml):

  3. Template Directory Index (.github/ISSUE_TEMPLATE/README.md):

    • Quick reference table listing all templates, filenames, purposes, and default labels.
  4. Updated Guidelines (CONTRIBUTING.md):

    • Updated bug reporting and feature request sections to link directly to GitHub's issue template chooser and docs/ISSUE_TEMPLATES.md.

Type of Change

  • 🐛 Bug fix (non-breaking change which fixes an issue)
  • ✨ New feature (non-breaking change which adds functionality)
  • 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • 📚 Documentation update
  • 🔧 Configuration change
  • ♻️ Refactoring (no functional changes)
  • 🎨 Style/UI changes

Related Issues

Fixes #441


Screenshots (if applicable)

N/A — Non-UI workflow configuration and documentation changes.


Checklist

  • My code follows the project's style guidelines
  • I have performed a self-review of my code
  • I have commented my code where necessary
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have tested my changes locally
  • Any dependent changes have been merged and published

Additional Notes

All templates strictly utilize GitHub Classic Markdown (.md) format with pre-populated editor text areas to maintain frictionless DX, offline portability, and consistency with .github/PULL_REQUEST_TEMPLATE.md.

@netlify

netlify Bot commented Aug 3, 2026

Copy link
Copy Markdown

👷 Deploy request for arcmind-ai pending review.

Visit the deploys page to approve it

Name Link
🔨 Latest commit b503033

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[ENHANCEMENT]: Add standardized GitHub Classic Markdown Issue Templates

2 participants