Skip to content

ci(station): require hardware evidence for host preparation #7193

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

Merged
cv merged 14 commits into from
Jul 20, 2026
Merged

ci(station): require hardware evidence for host preparation #7193

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
14 commits
Select commit Hold shift + click to select a range
e027039
ci(station): require hardware evidence for host preparation
senthilr-nv Jul 19, 2026
533f34d
fix(ci): fail closed on truncated Station file listings
senthilr-nv Jul 19, 2026
45775c7
test(ci): reject stale station deferrals
senthilr-nv Jul 19, 2026
8770f04
Merge branch 'main' into codex/station-hardware-evidence-gate
cv Jul 19, 2026
34d0347
chore(ci): refresh hardware evidence checks
cv Jul 19, 2026
6f4f4f0
fix(ci): revalidate edited station evidence
senthilr-nv Jul 19, 2026
a17ca11
test(ci): reject pull requests as station follow-ups
senthilr-nv Jul 19, 2026
7368745
Merge branch 'main' into codex/station-hardware-evidence-gate
cv Jul 19, 2026
3142feb
fix(ci): pin station gate node runtime
senthilr-nv Jul 19, 2026
1db9e2e
fix(ci): revalidate newly posted station evidence
senthilr-nv Jul 19, 2026
3299a4d
Merge branch 'main' into codex/station-hardware-evidence-gate
cv Jul 19, 2026
d34026e
Merge branch 'main' into codex/station-hardware-evidence-gate
cjagwani Jul 20, 2026
04b19d5
merge: refresh station evidence branch
senthilr-nv Jul 20, 2026
4d8cb36
refactor(ci): use maintainer review for station evidence
senthilr-nv Jul 20, 2026
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
8 changes: 8 additions & 0 deletions .github/PULL_REQUEST_TEMPLATE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,6 +26,14 @@
- [ ] Sensitive-path review completed or maintainer-approved waiver recorded — reviewer/approval link/justification:
- [ ] Non-success, skipped, or missing CI check accepted by maintainer — check name, approval link, and follow-up issue:

## DGX Station Hardware Evidence
<!-- Required only when scripts/prepare-dgx-station-host.sh changes. Maintainers must review the linked evidence before approving or merging. This is human-reviewed evidence, not authenticated hardware provenance. Exceptional bypasses use existing repository governance and must be documented on the PR. -->
- [ ] Tested on DGX Station
- Tested commit:
- Station profile/scenario:
- Result:
- Supporting evidence:

## Verification
<!-- Check each applicable item only when supported by the requested evidence. Run targeted tests once per relevant change set and rerun after later edits or hook autofixes that can affect the tested behavior. Do not rerun hook-covered checks. -->
- [ ] PR description includes a `Signed-off-by:` line and every commit appears as `Verified` in GitHub
Expand Down
1 change: 1 addition & 0 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -266,5 +266,6 @@ Follow `.agents/skills/_shared/pr-follow-up.md`: after opening or pushing to a P
- Run targeted tests once per relevant change set, rerunning after later behavior-affecting edits or hook autofixes, and run `npm run docs` for doc changes
- Count successful normal hooks as verification; if hooks were skipped or unavailable, refresh `origin/main` and use `npm run check:diff`
- Follow PR template (`.github/PULL_REQUEST_TEMPLATE.md`)
- PRs that change `scripts/prepare-dgx-station-host.sh` must include reviewable DGX Station test evidence identifying the tested commit, Station profile or scenario, result, and a supporting link. Any maintainer may review the evidence; without acceptable evidence, the PR is not ready to approve or merge. Treat the evidence as human-reviewed, not authenticated hardware provenance. Exceptional bypasses use existing repository governance and must document the reason on the PR.
- No secrets, API keys, or credentials committed
- Limit open PRs to fewer than 10
Loading