chore: add issue templates for bug reports and feedback#56
Merged
Conversation
Adds .github/ISSUE_TEMPLATE/ with: - bug_report.yml — structured fields for repro steps, logs, Python version, OS, and CCE version to reduce back-and-forth on bug reports - feedback.yml — lightweight first-experience form to capture signal from users who tried CCE but wouldn't file a formal bug report - config.yml — disables blank issues and routes general questions to Discussions once that tab is enabled Addresses the contribution friction identified in issue elara-labs#31.
Contributor
There was a problem hiding this comment.
Pull request overview
This PR adds GitHub Issue Forms to lower the friction for users to report bugs or share first-time feedback, aligning with the goal in #31 to increase engagement from interested forks.
Changes:
- Added a structured Bug Report issue form that collects repro steps, logs, and environment/version info.
- Added a lightweight Feedback / First Experience issue form to capture early user sentiment and friction points.
- Disabled blank issues and routed general questions/discussion to GitHub Discussions via issue template config.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| .github/ISSUE_TEMPLATE/bug_report.yml | Adds a structured bug report form with required fields for faster triage. |
| .github/ISSUE_TEMPLATE/feedback.yml | Adds a lightweight feedback form to capture user outcomes and pain points. |
| .github/ISSUE_TEMPLATE/config.yml | Disables blank issues and adds a Discussions contact link for questions. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
fazleelahhee
approved these changes
May 6, 2026
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
bug_report.yml— structured fields for repro steps, logs, Python version, OS, and CCE version to reduce back-and-forth on bug reportsfeedback.yml— lightweight first-experience form to capture signal from users who tried CCE but wouldn't open a formal bug reportconfig.yml— disables blank issues and routes general questions to Discussions once that tab is enabledContext
Investigation in #31 found that the repo has 14 forks with 0 commits ahead of main — people are interested but have no low-friction path to engage. The blank issue box is one of the most well-documented drop-off points in open source. These templates remove that barrier.
Test plan
outcomeanduse-caseare required