Problem (one or two sentences)
Since #123, the repository ships both legacy Markdown issue templates and the newer YAML form templates for the same issue types, so “New issue” shows duplicate/conflicting choices and reporters don’t know which form to use.
Context (who is affected and when)
Anyone opening a new issue on Zoo-Code-Org/Zoo-Code. Especially visible when following CONTRIBUTING.md (which describes the newer Bug Report / Enhancement Request forms) while the old templates are still listed alongside them.
Reproduction steps
- Open https://github.com/Zoo-Code-Org/Zoo-Code/issues/new/choose
(or go to the repo → Issues → New issue).
- Observe the template list.
- Compare with the files under
https://github.com/Zoo-Code-Org/Zoo-Code/tree/main/.github/ISSUE_TEMPLATE
Permalink: https://github.com/Zoo-Code-Org/Zoo-Code/tree/abaf732bb7a96848a7c6f5dd2ce485b86bff086d/.github/ISSUE_TEMPLATE
Current contents include both:
- bug_report.md and bug_report.yml
- feature_request.md and feature_request.yml
plus add-provider-model.md, marketplace.yml, and config.yml.
Expected result
A single, clear set of issue templates (the current structured YAML forms described in CONTRIBUTING.md), with no duplicate “bug” / “feature” options, and optionally an empty template for special cases (e.g. a bug report created by an AI assistant folowing the yaml templates)
Actual result
Both the old Markdown templates and the new YAML forms appear, so users can pick either an outdated or the intended form for the same kind of report.
Variations tried (optional)
N/A — this is repository configuration, not runtime behavior.
App Version
N/A (repo config). Observed on main as of 2026-08-11.
API Provider (optional)
Not Applicable / Other
Model Used (optional)
N/A
Zoo Code Task Links (optional)
(none)
Relevant logs or errors (optional)
Directory listing of .github/ISSUE_TEMPLATE on main:
- add-provider-model.md
- bug_report.md
- bug_report.yml
- config.yml
- feature_request.md
- feature_request.yml
- marketplace.yml
CONTRIBUTING.md currently instructs contributors to use:
- “Enhancement Request” (plain language, user benefit)
- “Bug Report” (minimal repro + expected vs actual + version)
Suggested fix: remove or archive the legacy bug_report.md and feature_request.md (and any other superseded templates) so only the intended YAML forms remain, and keep config.yml aligned with that set.
Problem (one or two sentences)
Since #123, the repository ships both legacy Markdown issue templates and the newer YAML form templates for the same issue types, so “New issue” shows duplicate/conflicting choices and reporters don’t know which form to use.
Context (who is affected and when)
Anyone opening a new issue on Zoo-Code-Org/Zoo-Code. Especially visible when following CONTRIBUTING.md (which describes the newer Bug Report / Enhancement Request forms) while the old templates are still listed alongside them.
Reproduction steps
(or go to the repo → Issues → New issue).
https://github.com/Zoo-Code-Org/Zoo-Code/tree/main/.github/ISSUE_TEMPLATE
Permalink: https://github.com/Zoo-Code-Org/Zoo-Code/tree/abaf732bb7a96848a7c6f5dd2ce485b86bff086d/.github/ISSUE_TEMPLATE
Current contents include both:
plus add-provider-model.md, marketplace.yml, and config.yml.
Expected result
A single, clear set of issue templates (the current structured YAML forms described in CONTRIBUTING.md), with no duplicate “bug” / “feature” options, and optionally an empty template for special cases (e.g. a bug report created by an AI assistant folowing the yaml templates)
Actual result
Both the old Markdown templates and the new YAML forms appear, so users can pick either an outdated or the intended form for the same kind of report.
Variations tried (optional)
N/A — this is repository configuration, not runtime behavior.
App Version
N/A (repo config). Observed on main as of 2026-08-11.
API Provider (optional)
Not Applicable / Other
Model Used (optional)
N/A
Zoo Code Task Links (optional)
(none)
Relevant logs or errors (optional)
Directory listing of .github/ISSUE_TEMPLATE on main:
CONTRIBUTING.md currently instructs contributors to use:
Suggested fix: remove or archive the legacy bug_report.md and feature_request.md (and any other superseded templates) so only the intended YAML forms remain, and keep config.yml aligned with that set.