Skip to content

chore: set native issue types in the issue forms #23

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
stephane-segning wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore: set native issue types in the issue forms #23

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .github/ISSUE_TEMPLATE/dev-ticket.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,7 @@ name: Development Ticket
description: Implementation work, bugs, refactors, technical tasks, spikes, or operational work.
title: "[Ticket]: "
labels: ["ticket"]
type: Task

@lightbridge-assistant lightbridge-assistant Bot Aug 13, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 correctness

Invalid top-level type key breaks form

type is not a legal top-level key in a GitHub issue form. The schema for issue forms supports only name, description, title, labels, assignees, projects, and body (docs.github.com "Syntax for issue forms"). An unrecognized top-level key fails the form's YAML validation, so when a contributor opens this template GitHub refuses to load it (form configuration error), rendering the template — and this change's goal — unusable. Consider a legitimate mechanism such as the issue-types feature (repo/org-level) or a label, or verifying behavior in an actual repo before merging.

Evidence: Added line type: Task between labels: ["ticket"] and body:; GitHub issue-form schema documents no type top-level key.

Was this useful? React 👍/👎 to give us feedback

body:
- type: markdown
attributes:
Expand Down
1 change: 1 addition & 0 deletions .github/ISSUE_TEMPLATE/epic.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,7 @@ name: Epic
description: A large initiative spanning multiple stories with a meaningful business or technical objective.
title: "[Epic]: "
labels: ["epic"]
type: Epic

@lightbridge-assistant lightbridge-assistant Bot Aug 13, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 correctness

Invalid top-level type key breaks form

type is not a legal top-level key in a GitHub issue form (valid keys are name, description, title, labels, assignees, projects, body). Unknown top-level keys fail the form's YAML validation, so opening this template produces a form-configuration error and the template becomes unusable. Same defect as in dev-ticket.yml and user-story.yml.

Evidence: Added line type: Epic between labels: ["epic"] and body:; not in the documented issue-form top-level key set.

Was this useful? React 👍/👎 to give us feedback

body:
- type: markdown
attributes:
Expand Down
1 change: 1 addition & 0 deletions .github/ISSUE_TEMPLATE/user-story.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,7 @@ name: User Story
description: A user need or a valuable capability, with testable acceptance criteria.
title: "[Story]: "
labels: ["user-story"]
type: Story

@lightbridge-assistant lightbridge-assistant Bot Aug 13, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 correctness

Invalid top-level type key breaks form

type is not a legal top-level key in a GitHub issue form (valid keys are name, description, title, labels, assignees, projects, body). Unknown top-level keys fail the form's YAML validation, so opening this template yields a form-configuration error and the template becomes unusable. Same defect as in dev-ticket.yml and epic.yml.

Evidence: Added line type: Story between labels: ["user-story"] and body:; not in the documented issue-form top-level key set.

Was this useful? React 👍/👎 to give us feedback

body:
- type: markdown
attributes:
Expand Down