Loading…
A short voice session: one question, one follow-up, then instant feedback — up to 5 minutes.
The code can execute with the job's tokens, secrets, network access, and runner privileges. Keep untrusted validation separate from privileged release operations.
Build scripts and tests are executable input, not just files to inspect. Avoid checking out and executing an untrusted revision in a context that has privileged tokens. Use constrained permissions, isolated runners, and trusted handoffs that verify artifact origin. Also treat pull-request titles and other metadata as untrusted when inserting them into shell commands.