feat: add GitHub issue templates (bug report + feature request)#466
Merged
Conversation
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
1 participant
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.
What
Adds GitHub issue forms so the repo has a structured way to file bugs and feature requests:
.github/ISSUE_TEMPLATE/bug_report.yml— a YAML issue form with Aeon-specific fields: which skill, failure type (API error vs. sandbox limitation vs. config vs. output-format), where it ran (Actions cron / dashboard Run-now / local./aeon), repro steps +var, arender: shelllogs box, and a "did you get a notification?" dropdown. Required checkboxes confirm the reporter searched existing issues and redacted secrets..github/ISSUE_TEMPLATE/feature_request.yml— a form to propose a new skill / gateway / dashboard / core change, with a "would you open a PR?" field and a skill schedule/varshape input..github/ISSUE_TEMPLATE/config.yml— setsblank_issues_enabled: falseso new issues go through the chooser, plus contact links to the Quick start (#quick-start) and@aeonframeworkon X.Why
aaronjmars/aeonis a 512★ / 170-fork repo with active external contributors and zero issue templates — every bug report arrives in a different shape. Aeon's failure modes are specific (a skill name, whether it was an API error or a sandbox limitation, whether a notification fired) and "it failed" without those is hard to act on. The forms capture exactly those fields up front. Lowering onboarding/reporting friction for forkers is a priority for the project.This is repo-actions idea #4 from the 2026-06-12 action set (the top remaining autonomously-implementable community-health gap after CONTRIBUTING.md shipped in #465).
Changes
.github/ISSUE_TEMPLATE/bug_report.yml: new bug report issue form.github/ISSUE_TEMPLATE/feature_request.yml: new feature request issue form.github/ISSUE_TEMPLATE/config.yml: disable blank issues, add contact linksDocs-only / config-only — no skills,
aeon.yml, or taxonomy paths touched, so neither CI gate (ci-skills-json,ci-capabilities-parity) is affected. Noskills.jsonregen needed.Built autonomously by Aeon