chore(github): add a Test or CI Infrastructure issue template - #4340
Merged
Conversation
Blank issues carry no labels, so infrastructure reports land in the tracker untriaged — the labels an issue form declares are the only ones applied at creation time, and neither bug.yml nor rfc.yml fits a report about the repo's own tooling. Adds a third form covering the test suite, CI pipeline, build tooling, and dependency configuration, labelled type:test. Fields mirror how these reports are actually evaluated here: a problem statement, measured evidence (failing run, durations, failure counts), and an optional scope check for sibling cases.
Han5991
requested review from
cixzhang,
ejhammond and
imdreamrunner
as code owners
July 26, 2026 01:36
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
meta-cla
Bot
added
the
CLA Signed
github-actions
Bot
added
community
Drops the Area dropdown — neither bug.yml nor rfc.yml uses one — and adds the pre-submission checklist rfc.yml ends with, so the three forms read as one set. Description now leads with Astryx rather than "the repo", matching its siblings.
Contributor
PR Analysis ReportNo new or modified components detected. Bundle Size Summary
Accessibility AuditStatus: No accessibility violations detected. Generated by PR Enrichment workflow | View full report |
cixzhang
approved these changes
Jul 30, 2026
cixzhang
left a comment
cixzhang
left a comment
Contributor
There was a problem hiding this comment.
Thanks for improving the issue-triage flow here — a dedicated Test / CI Infrastructure template will make it much easier to route and act on those reports. Nice, low-friction addition!
github-actions
Bot
removed
the
needs:code-review
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Blank issues carry no labels, and nothing adds them afterwards — no workflow under
.github/workflows/declares anissuestrigger. Thelabels:an issue form declares in its front matter is the only label applied at creation time.Neither existing template covers a report about the repository's own tooling:
bug.ymlis for a defect in a shipped component and requires anAstryx Version;rfc.ymlis for a new component or API and requires accessibility and component-composition answers. So test, CI, and dependency reports fall through to a blank issue and land unlabelled — #4337, #4338, and #4339 this week.What
Adds
.github/ISSUE_TEMPLATE/infra.yml— "Test or CI Infrastructure", labelledtype:test, titled[Infra]to match[Bug]and[RFC].The structure follows
rfc.ymlso the three forms read as one set: a Before you submit block, Problem and Evidence required, Scope Check and Proposed Direction optional, and a pre-submission checklist.type:testis the closest label that already exists. A form naming a label that doesn't exist silently applies nothing, so this uses only what's already defined.Blank issues stay enabled — there is no
config.ymlin this directory and this PR doesn't add one.Verification
idand alabel, and the checklist options all carry alabel../scripts/add-copyright.sh --checkdoes not flag this file. (Note: the script scans the whole working tree, so locally it reports untracked build output underapps/docsite/public/— none of it git-tracked. On a clean CI checkout that noise is absent.)pnpm check:repopasses.The rendered form can only be confirmed after merge — GitHub serves issue templates from the default branch, so a PR branch can't preview it.
If there are fields, wording, or a different label you'd want in this form, say so and I'll fold them in.