You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Both fork-facing validation workflows fail at the checkout step before inspecting the submitted skill. actions/checkout now refuses to check out fork code from a pull_request_target workflow unless the workflow explicitly opts into the risk.
The exact submitted commit independently passes the repository's structure validator on an LF checkout, and the security scanner report is PASS with zero failures and zero warnings. The hosted workflows fail before either result can be produced.
Environment
OS: GitHub-hosted Ubuntu runner
Workflow trigger: pull_request_target
Checkout action: actions/checkout@v4
Additional context
The validation workflow currently executes scripts/validate-skills.mjs from the fork checkout because its working directory is pr. A fix should retain the security boundary and avoid executing fork-modified validator code with the base repository token; merely bypassing the checkout safeguard without restructuring would preserve the pwn-request risk.
Describe the bug
Both fork-facing validation workflows fail at the checkout step before inspecting the submitted skill. actions/checkout now refuses to check out fork code from a pull_request_target workflow unless the workflow explicitly opts into the risk.
To Reproduce:
Expected behavior:
Fork submissions should be checked out in a safe, read-only context and validated by trusted base-repository code, with results reported on the PR.
Supporting Material
The exact submitted commit independently passes the repository's structure validator on an LF checkout, and the security scanner report is PASS with zero failures and zero warnings. The hosted workflows fail before either result can be produced.
Environment
Additional context
The validation workflow currently executes scripts/validate-skills.mjs from the fork checkout because its working directory is pr. A fix should retain the security boundary and avoid executing fork-modified validator code with the base repository token; merely bypassing the checkout safeguard without restructuring would preserve the pwn-request risk.