Protocol
Review what a privileged workflow will actually execute
An unchanged workflow can still run changed scripts. Before authorizing a run with secrets or write access, inspect the code it will execute and the privileges it receives.
Before you use it
- Use when
- An agent-generated PR would trigger Actions or another pipeline that can access secrets or mutate infrastructure.
Keep this limit in mind
- Automated execution can be safe in carefully constrained environments; the requirement is a risk-appropriate authorization boundary, not manual clicking forever.
Current editorial reading
Trace the execution path
Review the trigger, checked-out revision, commands, referenced scripts and external actions, along with tokens, secrets and runner access. A package script changed in a pull request matters even when the workflow file did not change. Pin and review external actions according to the project’s security policy.
Check the real approval boundary
GitHub Copilot workflows require approval by default, but a repository can be configured for automatic runs. Verify the setting rather than assuming a waiting button exists. Keep untrusted code out of privileged execution; restricted test environments need their own isolation checks. Human approval is a decision about a bounded run, not proof that it cannot cause harm.
Take it with you
Record the revision, execution path, privileges, reviewer and decision. Recheck changes that alter those facts; a safe-looking YAML diff is not enough.
Sources and evidence (3)
What we checked
Copilot workflow approval is the default, with an option for automatic execution.
Live official documentation inspected on 2026-10-04. Product defaults can change and actual repository configuration governs.
Review output from Copilot · Manage GitHub Actions workflow runs
Build and package scripts are security-sensitive executable surfaces.
Selected official passage inspected. The full execution-path review is an editorial adaptation.
Secure Coding with AI Cheat Sheet · Secure Coding with AI, section 10
Checking out untrusted code in a privileged workflow can expose secrets and repository access.
Selected current official guidance inspected on 2026-10-04; neither sandboxing nor an approval click is a universal safety proof.
GitHub Actions secure use reference · Mitigating the risks of untrusted code checkout
Editorial sources (3)
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingReview what a privileged workflow will actually execute
Ideas that link here
These ideas link to this one. Check their conditions and limits before use.
Use before this ideaKeep CI agents away from production secrets they do not need
Original edition evidence and sources
These records belong to the original released edition. The current editorial reading has its own evidence above; neither set silently replaces the other.
GitHub documentation says Copilot agent pull requests should receive the same thorough review as other contributions and warns reviewers to inspect workflow changes before allowing privileged Actions runs.
This is GitHub-specific implementation guidance; the general pattern is independent review before privileged execution.
Review output from Copilot · Review Copilot's changes; Manage GitHub Actions workflow runs
OWASP treats rules files, build scripts, CI workflows and package lifecycle scripts as security-sensitive control surfaces that deserve heightened review when an agent changes them.
The exact sensitive-file set depends on the repository and build system.
Secure Coding with AI Cheat Sheet · Rules Files; Prompt-to-Code Supply Chain Risk
All sources (2)
Original edition, downloads and provenance
The reading above is editorial version 1.0.0, bound to this exact source edition. The original data and saved downloads retain that edition and the separate editorial layer. They may contain earlier wording; use the current reading above when interpreting it.
Version 0.1.0
No review details are supplied for this edition.
Read the original edition and overlay as JSON · Release details