Protocol

Review workflow execution separately from feature correctness

A correct feature can arrive with a dangerous workflow change. Decide whether the pipeline may run with its proposed authority before treating passing tests as approval.

About 2 min read

Before you use it

Use when
  • An agent edits CI/CD configuration as part of another task.

Keep this limit in mind

  • Exact controls depend on CI platform; apply the same principle to any pipeline with credentials or deployment authority.

Current editorial reading

Inspect what the workflow can do

Highlight changes to workflow triggers, token permissions, secrets, third-party actions and deployment steps. Ask the responsible owner to review the changed authority. For example, a move from read to write permissions needs an explicit reason and an appropriate review gate, even when the application tests pass.

Check the gate that is actually configured

GitHub distinguishes approval to run Copilot pull-request workflows from approval to merge the pull request. Its documented default waits for workflow approval, but configuration can allow automatic runs. A workflow edit is therefore not universally prevented from running or merging by GitHub itself. Verify the active run and merge controls in the repository.

Take it with you

Before approving the next run, identify its secrets and permissions and the person or policy authorizing them. Keep evidence of that review separate from the feature’s test result.

Sources and evidence (2)

What we checked

Supports

GitHub documents separate pull-request review and workflow-run approval, with a default approval pause and an optional automatic-run configuration.

Selected current GitHub Docs sections read on 2026-10-04. No repository settings or actual workflow execution were inspected or changed.

Review output from Copilot · Review Copilot’s changes; Manage GitHub Actions workflow runs

Supports

OWASP recommends explicit review and approval gates for sensitive pipeline changes and access.

Selected sections 7, 10 and 11 read on 2026-10-04. This is security guidance, not evidence that every platform already enforces those gates.

Secure Coding with AI Cheat Sheet · Out-of-Scope Edits and Review Anchoring; Prompt-to-Code Supply Chain Risk; CI/CD Agents and Confused Deputy Risk

Limits

The documented ability to configure automatic workflow runs limits any claim that GitHub universally blocks a changed pipeline until separate human approval.

The draft makes a recommended review boundary explicit and avoids presenting it as an unconditional product restriction or merge rule.

Review output from Copilot · Manage GitHub Actions workflow runs, final paragraph

Editorial sources (2)

Editorial version 1.0.0 · Evidence checked 2026-10-04

Save and practise this idea

My learning

Read. Recall. Repeat.

Save this idea and return to it on any device.

Use email
Keep exploring

Connected ideas

You are readingReview workflow execution separately from feature correctness

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.

Supports

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

Supports

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

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