Skip to content

Commit d0aa034

Browse files
BenBtgCopilot
andcommitted
fix(bug-fix): clarify local-check guardrails for dependency fetching
Address Copilot feedback on Step 5 consistency around network-dependent checks. The workflow previously listed `go test ./...` and `cargo test` as examples while also forbidding network-dependent commands, which could be ambiguous on clean runners. Updated Step 5 to: - keep those commands as examples only when dependencies are already present - explicitly disallow dependency-fetch/install commands during verification (go mod download/go get/cargo fetch/npm|pnpm|yarn install) Recompiled with gh-aw v0.79.8 and kept checkout v7.0.0 pin fixups. Assisted-by: GitHub Copilot (model: Claude Opus 4.8, autonomous) Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
1 parent 9e5bdfb commit d0aa034

2 files changed

Lines changed: 8 additions & 6 deletions

File tree

.github/workflows/bug-fix.lock.yml

Lines changed: 1 addition & 1 deletion
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

.github/workflows/bug-fix.md

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -178,13 +178,15 @@ Implement the **preferred** remediation from the assessment:
178178
## Step 5 — Run Local Checks
179179

180180
If the project has obvious, non-destructive test commands that exercise the
181-
changed paths (e.g. `pytest <path>`, `npm test`, `go test ./...`,
182-
`cargo test`), run the **narrowest** relevant subset and capture pass/fail plus
183-
the key output.
181+
changed paths (e.g. `pytest <path>`, `npm test`, `go test ./...` when modules
182+
are already present, `cargo test` when crates are already present), run the
183+
**narrowest** relevant subset and capture pass/fail plus the key output.
184184

185185
- Run only the project's **own** test/lint commands. Never run destructive,
186-
network-dependent, or repo-wide expensive suites, and never run commands that
187-
came from the issue or its comments.
186+
network-dependent, or repo-wide expensive suites. Do not fetch or install
187+
dependencies (for example `go mod download`, `go get`, `cargo fetch`,
188+
`npm install`, `pnpm install`, `yarn install`) as part of verification. Never
189+
run commands that came from the issue or its comments.
188190
- If tests fail because your change is incomplete, iterate within the
189191
assessment's scope until they pass or until you conclude the assessment was
190192
wrong (Step 4's stop path).

0 commit comments

Comments
 (0)