[Bug Reporting]: Create issue templates #152
Description
Topic
It would be nice to support the reporting and contribution by providing issue templates for different purposes.
To help the user to focus on the necessary information for the issue type
Some examples
Bug Report
Documentation Bug
Feature Request
Feature Suggestion/Discussion
feature_discussion.yml
This is requested by the project documentation but maybe this better has to be linked to a discussion board as suggested below.
The common place would be GitHub Feedback other possible locations are listet below.
| Platform | Correct Link | Notes / Status (as of April 2025) | Existing |
|---|---|---|---|
| GitHub Feedback | https://github.com/community/community/discussions/categories/copilot-product-feedback | This could be the official place for feedback, questions, ideas, and usage help | Unused yet |
| GitHub Discussions | https://github.com/github/copilot-sdk/discussions | This is the official place for questions, ideas, and usage help | No |
| Issues | https://github.com/github/copilot-sdk/issues | For bug reports & feature requests only (use templates) | Yes |
| Stack Overflow | https://stackoverflow.com/questions/tagged/github-copilot-sdk | Use this tag for public questions (growing community) | Unused yet |
| Official Docs | https://docs.github.com/en/copilot/github-copilot-sdk | Main documentation hub | No |
| Microsoft Q&A | https://learn.microsoft.com/en-us/answers/tags/219/github-copilot-sdk | Alternative Microsoft-hosted Q&A (less traffic) | No |
Distinction Enforcement
If a "Feature Discussion" issue converges on a concrete spec, convert it to a "Feature Request" (edit title/labels) or close it and open a new Request referencing the discussion.
Operational Notes
Common Pitfall to Avoid
Do not create templates for "Question" or "Support"—that trains users to open issues for help. Redirect those to GitHub Discussions or Stack Overflow via config.yml contact links.
The links in config.yaml have to be edited or created accordingly to the project
Migration Strategy
Existing issues won’t be affected. Pin a meta-issue explaining the new system for one week before enforcing blank_issues_enabled: false.
Auto-labeling
The labels field in each YAML automatically tags issues, enabling maintainers to filter by needs-triage or rfc.
Template Fatigue
Monitor if users ignore fields. If "Environment Details" is often left empty despite being optional, make it required or remove it.