Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
109 changes: 109 additions & 0 deletions .github/ISSUE_TEMPLATE/bug_report.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,109 @@
name: Bug report
description: Report a reproducible XAIOS defect or regression.
title: "[Bug]: "
labels:
- type: bug
- needs: triage
Comment on lines +4 to +6

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Quote colon-bearing labels as strings

GitHub issue forms expect labels to be an array or comma-delimited string of label names, but these unquoted entries parse as YAML maps ({"type":"bug"}, {"needs":"triage"}) rather than the intended label strings. In repositories using these new forms, this makes the template metadata invalid or prevents the automatic labels from being applied; the same labels pattern is repeated in the other issue-form files and should be quoted, e.g. "type: bug".

Useful? React with 👍 / 👎.

body:
- type: markdown
attributes:
value: |
Use this for reproducible defects in XAIOS. Include the smallest relevant validation command and any QEMU output or CI link.
- type: textarea
id: summary
attributes:
label: Summary
description: One or two sentences describing the observed problem.
placeholder: "Example: qemu-smoke fails after VirtIO block initialization."
validations:
required: true
- type: textarea
id: objective
attributes:
label: Problem / objective
description: What is wrong, what should happen instead, and why it matters.
validations:
required: true
- type: dropdown
id: subsystem
attributes:
label: Relevant subsystem
multiple: true
options:
- boot/UEFI
- kernel core
- memory management
- VirtIO/PCI
- filesystem/persistence
- networking/SSH
- userspace
- CPU-AI runtime
- model arena
- security/sandboxing
- CI/gates
- docs/contracts
- hardware readiness
validations:
required: true
- type: textarea
id: acceptance
attributes:
label: Acceptance criteria
description: Checklist that proves the bug is fixed.
value: |
- [ ] Reproducer is documented.
- [ ] Root cause is identified or bounded.
- [ ] Fix is covered by the smallest relevant gate.
validations:
required: true
- type: dropdown
id: validation
attributes:
label: Validation command or gate
multiple: true
options:
- make bootstrap
- make compile-check
- make all
- make image
- make qemu-smoke
- make qemu-abi-contract
- make qemu-readiness-gate
- make qemu-full-os-rc
- make qemu-network-suite
- make qemu-ssh-smoke
- make intel-desktop-gate
- docs-only
- manual-review
validations:
required: true
- type: dropdown
id: risk
attributes:
label: Risk level
options:
- Low
- Medium
- High
- Security
- Hardware
- Performance Claim
- API/Contract
validations:
required: true
- type: textarea
id: dependencies
attributes:
label: Dependencies / blockers
description: List blockers, related issues, missing evidence, or required human decisions.
placeholder: "Blocked by: ..."
- type: textarea
id: related
attributes:
label: Related docs or source files
description: Include paths such as kernel/user/syscall.c, contracts/qemu-rc-v1.json, or scripts/qemu-smoke.py.
placeholder: |
- kernel/user/syscall.c
- scripts/qemu-smoke.py
validations:
required: true
2 changes: 2 additions & 0 deletions .github/ISSUE_TEMPLATE/config.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@
blank_issues_enabled: true
contact_links: []
108 changes: 108 additions & 0 deletions .github/ISSUE_TEMPLATE/docs_contracts.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,108 @@
name: Documentation / contracts issue
description: Track documentation, ABI/API contract, hardware-readiness, or roadmap consistency work.
title: "[Docs/Contracts]: "
labels:
- type: docs
- area: docs-contracts
body:
- type: markdown
attributes:
value: |
Use this for documentation, contract, release-candidate evidence, and hardware-readiness alignment work. Do not use QEMU-only results as hardware performance proof.
- type: textarea
id: summary
attributes:
label: Summary
description: One or two sentences describing the docs/contracts problem.
validations:
required: true
- type: textarea
id: objective
attributes:
label: Problem / objective
description: What must be clarified, reconciled, or documented.
validations:
required: true
- type: dropdown
id: subsystem
attributes:
label: Relevant subsystem
multiple: true
options:
- boot/UEFI
- kernel core
- memory management
- VirtIO/PCI
- filesystem/persistence
- networking/SSH
- userspace
- CPU-AI runtime
- model arena
- security/sandboxing
- CI/gates
- docs/contracts
- hardware readiness
validations:
required: true
- type: textarea
id: acceptance
attributes:
label: Acceptance criteria
description: Checklist defining done.
value: |
- [ ] Current source/config is inspected before changing docs or contracts.
- [ ] Stale or conflicting claims are reconciled or explicitly marked as unresolved.
- [ ] Validation command or docs-only review path is documented.
validations:
required: true
- type: dropdown
id: validation
attributes:
label: Validation command or gate
multiple: true
options:
- make bootstrap
- make compile-check
- make all
- make image
- make qemu-smoke
- make qemu-abi-contract
- make qemu-readiness-gate
- make qemu-full-os-rc
- make qemu-network-suite
- make qemu-ssh-smoke
- make intel-desktop-gate
- docs-only
- manual-review
validations:
required: true
- type: dropdown
id: risk
attributes:
label: Risk level
options:
- Low
- Medium
- High
- Security
- Hardware
- Performance Claim
- API/Contract
validations:
required: true
- type: textarea
id: dependencies
attributes:
label: Dependencies / blockers
description: List human decisions, measurements, source changes, or related issues required first.
- type: textarea
id: related
attributes:
label: Related docs or source files
description: Include relevant source, docs, contracts, or scripts.
placeholder: |
- docs/API.md
- contracts/qemu-rc-v1.json
- HARDWARE-READINESS.md
validations:
required: true
104 changes: 104 additions & 0 deletions .github/ISSUE_TEMPLATE/engineering_task.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,104 @@
name: Engineering task
description: Track implementation, refactoring, validation, CI, or release-readiness work.
title: "[Task]: "
labels:
- type: task
- needs: triage
body:
- type: markdown
attributes:
value: |
Use this for concrete engineering work. Prefer small, reviewable changes with explicit non-goals and validation gates.
- type: textarea
id: summary
attributes:
label: Summary
description: One or two sentences describing the task.
validations:
required: true
- type: textarea
id: objective
attributes:
label: Problem / objective
description: What must be changed or verified, and why.
validations:
required: true
- type: dropdown
id: subsystem
attributes:
label: Relevant subsystem
multiple: true
options:
- boot/UEFI
- kernel core
- memory management
- VirtIO/PCI
- filesystem/persistence
- networking/SSH
- userspace
- CPU-AI runtime
- model arena
- security/sandboxing
- CI/gates
- docs/contracts
- hardware readiness
validations:
required: true
- type: textarea
id: acceptance
attributes:
label: Acceptance criteria
description: Checklist defining done.
value: |
- [ ] Current source/config is inspected before implementation.
- [ ] Change is scoped to the stated subsystem and non-goals.
- [ ] Relevant validation command is run or skipped with a clear reason.
validations:
required: true
- type: dropdown
id: validation
attributes:
label: Validation command or gate
multiple: true
options:
- make bootstrap
- make compile-check
- make all
- make image
- make qemu-smoke
- make qemu-abi-contract
- make qemu-readiness-gate
- make qemu-full-os-rc
- make qemu-network-suite
- make qemu-ssh-smoke
- make intel-desktop-gate
- docs-only
- manual-review
validations:
required: true
- type: dropdown
id: risk
attributes:
label: Risk level
options:
- Low
- Medium
- High
- Security
- Hardware
- Performance Claim
- API/Contract
validations:
required: true
- type: textarea
id: dependencies
attributes:
label: Dependencies / blockers
description: List blockers, sequencing constraints, missing hardware, or required human decisions.
- type: textarea
id: related
attributes:
label: Related docs or source files
description: Include relevant source, docs, contracts, or scripts.
validations:
required: true
Loading
Loading