issue-creation

GitHub issue creation requires enforcing template selection and pre-flight checks to guide contributors through mandatory fields. This ensures maintainers receive consistent, high-quality requests without rework or missing context before implementation begins.

Issue-first triage is a workflow that enforces searching for duplicates, picking bug or feature templates, and filling mandatory fields before submission. It guarantees new issues are tagged with status:needs-review and await maintainer approval.

Automated labeling and checkpoints guarantee each new GitHub issue is tagged with status:needs-review during bug reporting. The issue waits for a maintainer to add status:approved, keeping the approval workflow structured and consistent.

Yes, the issue triage process works with both bug reports and feature requests. It enforces searching for duplicates and picking the appropriate template, ensuring every mandatory field is filled before a maintainer reviews the submission.

A maintainer decision tree clarifies when to approve, close, or redirect GitHub issue submissions to discussions. This ensures only scoped work becomes PRs, maintaining structured approval workflows and consistent priority tags across the repository.

GitHub issue creation fails without duplicate searches and template validation because it leads to fragmented issue intake. Enforcing pre-flight checks and mandatory fields prevents missing context, eliminating rework for maintainers receiving the requests.