Chore: Create issue templates (bug report, feature request)#288
Merged
Conversation
Contributor
Author
|
@Xhristin3 Kindly go through. |
Xhristin3
approved these changes
Jun 18, 2026
Xhristin3
left a comment
Contributor
There was a problem hiding this comment.
Thanks for setting up the issue templates — this will go a long way toward keeping our bug reports and feature requests structured. Approving and merging!
4 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Added structured GitHub issue templates to replace the default blank text box. Contributors are now guided through required fields when filing bugs or requesting features. Blank issues are disabled via
config.ymlto enforce template use.Closes #209
Type of change
Testing performed
No code changes — new YAML files only. Verified locally:
All 4 packages — 0 errors, 0 new warnings
cd api && npm run lint && npx tsc --noEmit
cd xstreamroll-sdk && npm run lint && npx tsc --noEmit
cd xstreamroll-processing && npm run lint && npx tsc --noEmit
cd app && npm run lint && npx tsc --noEmit
Final verification on GitHub: open a new issue and confirm the template chooser appears, blank issue link is absent, and required fields block empty submission.
Screenshots (if applicable)
N/A — no UI changes.
Checklist — author
origin/mainand resolved conflicts.npm run lint,npm run build,npm test.Checklist — reviewer guidance
The two unchecked checklist items (tests and documentation) are intentionally left unchecked — there are no tests to write for YAML template files, and no public behavior changed that needs documenting.