Conversation
… lockfiles Agent-Logs-Url: https://github.com/github/gh-aw/sessions/87e804d1-7b3e-49b7-abf4-2ea07aff1cfe Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Agent-Logs-Url: https://github.com/github/gh-aw/sessions/87e804d1-7b3e-49b7-abf4-2ea07aff1cfe Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
untrusted_checkout_exec findings in workflow_call smoke lockfiles
|
@copilot update the compiler code that generates those steps |
Agent-Logs-Url: https://github.com/github/gh-aw/sessions/c8f7005c-21c3-4652-a120-3ef8ddb95f74 Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Agent-Logs-Url: https://github.com/github/gh-aw/sessions/c8f7005c-21c3-4652-a120-3ef8ddb95f74 Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Updated to generate this in compiler code: added Warning Firewall rules blocked me from connecting to one or more addresses (expand for details)I tried to connect to the following addresses, but was blocked by firewall rules:
If you need me to access, download, or install something from one of these locations, you can either:
|
untrusted_checkout_exec findings in workflow_call smoke lockfilesuntrusted_checkout_exec suppression for workflow_call save-base steps
There was a problem hiding this comment.
Pull request overview
This PR fixes newly reported poutine static-analysis untrusted_checkout_exec findings by ensuring the workflow compiler consistently emits an explicit suppression comment for the “save base GitHub folders” step that runs a trusted setup script from ${RUNNER_TEMP}/gh-aw/actions/.
Changes:
- Updated the workflow compiler to generate
# poutine:ignore untrusted_checkout_execimmediately before runningsave_base_github_folders.sh. - Recompiled the affected
workflow_callsmoke workflow lockfiles so the generated suppression is present. - Updated workflow compiler golden fixtures to match the newly generated YAML.
Show a summary per file
| File | Description |
|---|---|
pkg/workflow/pr.go |
Adds generation of the poutine suppression comment for the save-base step. |
.github/workflows/smoke-workflow-call.lock.yml |
Regenerated lockfile to include the suppression on the relevant step. |
.github/workflows/smoke-workflow-call-with-inputs.lock.yml |
Regenerated lockfile to include the suppression on the relevant step. |
pkg/workflow/testdata/TestWasmGolden_CompileFixtures/basic-copilot.golden |
Updates golden output to reflect the new generated suppression line. |
pkg/workflow/testdata/TestWasmGolden_CompileFixtures/with-imports.golden |
Updates golden output to reflect the new generated suppression line. |
Copilot's findings
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 5/5 changed files
- Comments generated: 0
Daily static analysis reported new
poutineuntrusted_checkout_execfindings in the two workflow_call smoke workflows. The flagged executions were trusted setup scripts under${RUNNER_TEMP}/gh-aw/actions/but were missing explicit suppressions on one step in each lockfile.Problem context
untrusted_checkout_execfindings in:.github/workflows/smoke-workflow-call.lock.yml.github/workflows/smoke-workflow-call-with-inputs.lock.ymlChange made
pkg/workflow/pr.goingenerateSaveBaseGitHubFoldersStepto emit:# poutine:ignore untrusted_checkout_exec.github/workflows/smoke-workflow-call.lock.yml.github/workflows/smoke-workflow-call-with-inputs.lock.ymlpkg/workflow/testdata/TestWasmGolden_CompileFixtures/basic-copilot.goldenpkg/workflow/testdata/TestWasmGolden_CompileFixtures/with-imports.goldenWhy this location
save_base_github_folders.shfrom${RUNNER_TEMP}/gh-aw/actions/, populated by the trusted setup action in the same job, matching the intended suppression criteria from the report.