Summary

The repository has no .github/ISSUE_TEMPLATE/ directory. When users or contributors open an issue, they get an empty form. Adding structured issue templates ensures consistent, high-quality bug reports and feature requests.

What to add

Create .github/ISSUE_TEMPLATE/ with at least two templates:

1. bug_report.yml

Fields:

• Title prefix — auto-prepend bug:
• Description — what happened vs. what was expected
• Reproduction — minimal .ez code that triggers the bug
• System info — output of ez report (OS, CPU, RAM, C compiler, EZ version)
• Severity — dropdown: crash, incorrect output, misleading error, cosmetic

2. feature_request.yml

Fields:

• Title prefix — auto-prepend feat:
• Description — what the feature should do
• Use case — why this is needed
• Alternatives considered — other approaches

3. config.yml (optional)

Add a blank issues link or contact link if desired.

Reference

• CONTRIBUTING.md already describes the expected bug report format — mirror it in the template
• GitHub docs on YAML issue forms: https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests

Files to create

• .github/ISSUE_TEMPLATE/bug_report.yml
• .github/ISSUE_TEMPLATE/feature_request.yml
• .github/ISSUE_TEMPLATE/config.yml (optional)