chore: add issue templates#368
Conversation
Greptile SummaryAdds three GitHub issue template files to standardize how bugs and contribution proposals are submitted, while disabling blank issues and redirecting questions to Discord.
Confidence Score: 4/5Safe to merge; the only change is adding GitHub issue template YAML files with no runtime impact. The contribution proposal template leaves
Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[User opens new issue] --> B{Select template}
B --> C[Bug Report\nbug.yml]
B --> D[Contribution Proposal\ncontribution.yml]
B --> E[Questions / Discussion\nconfig.yml contact_link]
C --> F[Requires: description + repro steps\nOptional: expected behavior + version\nAuto-label: bug]
D --> G[Requires: what + why\nOptional: how\nAuto-label: none]
E --> H[Redirected to Discord\nhttps://discord.gg/WZFjaP6Gt8]
B --> I{blank_issues_enabled: false}
I --> J[Blank issues disabled]
Prompt To Fix All With AIFix the following 1 code review issue. Work through them one at a time, proposing concise fixes.
---
### Issue 1 of 1
.github/ISSUE_TEMPLATE/contribution.yml:3
Empty labels array means contribution proposals won't be automatically tagged when submitted. Unlike `bug.yml` which applies the `"bug"` label, these issues will have no label, making them harder to filter and triage in the issue tracker.
```suggestion
labels: ["proposal"]
```
Reviews (1): Last reviewed commit: "chore: add issue templates" | Re-trigger Greptile |
| @@ -0,0 +1,34 @@ | |||
| name: Contribution Proposal | |||
| description: Propose a change or feature before opening a larger PR | |||
| labels: [] | |||
There was a problem hiding this comment.
Empty labels array means contribution proposals won't be automatically tagged when submitted. Unlike
bug.yml which applies the "bug" label, these issues will have no label, making them harder to filter and triage in the issue tracker.
| labels: [] | |
| labels: ["proposal"] |
Prompt To Fix With AI
This is a comment left during a code review.
Path: .github/ISSUE_TEMPLATE/contribution.yml
Line: 3
Comment:
Empty labels array means contribution proposals won't be automatically tagged when submitted. Unlike `bug.yml` which applies the `"bug"` label, these issues will have no label, making them harder to filter and triage in the issue tracker.
```suggestion
labels: ["proposal"]
```
How can I resolve this? If you propose a fix, please make it concise.There was a problem hiding this comment.
Good call. I added the existing enhancement label so contribution proposal issues are automatically tagged for triage. I used enhancement instead of proposal because the repo does not currently have a proposal label.
Responded by Pi using GPT-5.
Summary
Validation
oxfmt --writeon the staged YAML filesThis PR description was generated by Pi using GPT-5