Skip to content

feat: add GitHub issue templates for bugs, features, and questions#184

Merged
EMaher merged 6 commits into
mainfrom
emaher-add-issue-templates
Jun 24, 2026
Merged

feat: add GitHub issue templates for bugs, features, and questions#184
EMaher merged 6 commits into
mainfrom
emaher-add-issue-templates

Conversation

@EMaher

@EMaher EMaher commented Jun 23, 2026

Copy link
Copy Markdown
Contributor

Why

The repo has no issue templates, which means bug reports and feature requests arrive in inconsistent formats. Adding structured YAML issue forms gives contributors clear guidance and ensures we capture the right details up front.

What this adds

Three YAML-based issue form templates under .github/ISSUE_TEMPLATE/:

  • bug-report.yml (auto-labels: bug) -- Captures the command, expected/actual behavior, npm package version (with instructions on how to find it), environment details, CI/CD platform, and whether the bug is blocking.
  • feature-request.yml (auto-labels: type:feature) -- Captures the problem/use case, proposed solution, and optionally which command is affected.
  • question.yml (auto-labels: question) -- Simple form for usage questions with optional context.

Notes

  • Uses GitHub's modern YAML issue form syntax (dropdowns, inputs, textareas with validation) rather than the older markdown template format.
  • Labels are applied automatically via the labels: key in each template.
  • All required fields have validations.required: true so incomplete submissions are caught early.

EMaher added 3 commits June 22, 2026 21:13
Adds YAML-based issue forms:
- bug-report.yml (labels: bug)
- feature-request.yml (labels: type:feature)
- question.yml (labels: question)
@EMaher EMaher marked this pull request as ready for review June 23, 2026 16:50
@EMaher EMaher assigned azaslonov and EMaher and unassigned azaslonov Jun 23, 2026
@EMaher EMaher requested review from azaslonov and Copilot June 23, 2026 16:52

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds GitHub YAML issue forms to standardize how contributors submit bug reports, feature requests, and questions, improving triage signal and ensuring key details are captured up front.

Changes:

  • Introduces a Bug Report issue form capturing command, expected/actual behavior, version, environment details, CI/CD context, and blocking status.
  • Introduces a Feature Request issue form capturing problem/use case, proposed solution, and optionally the affected command.
  • Introduces a Question issue form capturing the question and optional context.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File Description
.github/ISSUE_TEMPLATE/bug-report.yml New bug-report issue form (command/behavior/version/environment/CI-CD/blocking).
.github/ISSUE_TEMPLATE/feature-request.yml New feature-request issue form (problem/solution/affected command).
.github/ISSUE_TEMPLATE/question.yml New question issue form (question + optional context).

Comment thread .github/ISSUE_TEMPLATE/bug-report.yml Outdated
Comment thread .github/ISSUE_TEMPLATE/feature-request.yml Outdated
EMaher and others added 2 commits June 23, 2026 11:09
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Comment thread .github/ISSUE_TEMPLATE/bug-report.yml Outdated
Comment thread .github/ISSUE_TEMPLATE/bug-report.yml
@EMaher

EMaher commented Jun 23, 2026

Copy link
Copy Markdown
Contributor Author

@copilot have squad handle comments.

@EMaher EMaher merged commit 732a8e4 into main Jun 24, 2026
5 checks passed
@EMaher

EMaher commented Jun 24, 2026

Copy link
Copy Markdown
Contributor Author

Related to #90

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.

4 participants