skip to content

Copilot cloud agent pushed commits to its pull request, but none of the repository's GitHub Actions workflows ran. Why, and what changes that?

level: middleimportance: should knowfreq 9%

answer

  1. not a broken trigger
  2. workflows can hold secrets
  3. a button in the merge box
  4. a human with write access decides
  5. Actions workflow approval section

basics

~20 s

By default, workflows do not run on Copilot cloud agent's pushes until a user with write access reviews the changes and clicks Approve and run workflows. An administrator can turn off Require approval for workflow runs, letting unreviewed code run.

solid answer

~40 s

It is the default, not a fault. GitHub does not trigger Actions workflows on Copilot cloud agent's pushes until someone with write access has looked at the code and clicked **Approve and run workflows** in the pull request's merge box. Workflows can be privileged and can read secrets, so the docs ask you to inspect the diff first, especially any change under `.github/workflows/`. A repository administrator can remove the hold under **Settings > Copilot > Cloud agent**, in the "Actions workflow approval" section, by turning off **Require approval for workflow runs**; GitHub warns this may let unreviewed code written by Copilot gain write access to the repository or reach its Actions secrets. Approving runs only releases the checks; the pull request still needs a human to mark it ready, approve and merge.

go deeper

for a junior

Recall that workflows on Copilot cloud agent's pull requests wait for a person with write access to click Approve and run workflows.

for a middle

Explain why: workflows can be privileged and read secrets, and Copilot's code is unreviewed when pushed. Know the Require approval for workflow runs setting and who may change it.

for a senior

Show the review habit before approving: read workflow-file and build-script changes first, and decide per repository whether its workflows' secrets and write permissions make dropping the approval acceptable.

for a principal

Frame the setting as a policy choice across repositories: where approval friction is worth keeping, and how automations that open issues and pull requests interact with it.

## The default: workflows wait for a person When **Copilot cloud agent** pushes commits to a pull request, the repository's **GitHub Actions workflows** (CI builds, tests, deploy previews) do **not** start on their own. Instead, the pull request's merge box offers an **Approve and run workflows** button. Only a user with **write access** to the repository can click it. So the symptom "Copilot's pull request has no checks" usually means nobody has approved the runs yet. Nothing is wrong with the workflow triggers. ## Why GitHub holds them A workflow is code that runs with the repository's permissions. The docs give the reasons for the hold plainly: - Workflows **can be privileged** and can have access to **sensitive secrets**. - Copilot's changes have not been reviewed yet when it pushes. - The pull request may itself **change workflow files**; the docs single out edits under `.github/workflows/` as the ones to watch. - An approved run executes the code on the pull request branch, so approving is a trust decision about that code. The same rule protects **automations**: an issue or pull request opened by one automation could trigger another, and because workflows on a Copilot pull request still wait for a write-access approval, such a chain cannot run workflows by itself. ## Approving a run 1. Open the pull request Copilot created or updated. 2. Read the diff, paying particular attention to workflow files, build scripts and dependency changes. 3. In the merge box, click **Approve and run workflows**. 4. Watch the checks as usual; later pushes from Copilot are held again unless the setting below is changed. ## Turning the hold off A **repository administrator** can let workflows run without that click: 1. Open the repository's **Settings**. 2. Under "Code, planning, and automation", choose **Copilot**, then **Cloud agent**. 3. In the **Actions workflow approval** section, disable **Require approval for workflow runs**. GitHub attaches a warning to this setting: running workflows without approval **may allow unreviewed code written by Copilot to gain write access to your repository or access your GitHub Actions secrets**. A sensible test before turning it off is whether the repository's workflows hold secrets worth stealing or can write back to the repository; if either is true, keep the approval. ## What the hold does and does not do | Question | Answer | |---|---| | Does approving runs approve the pull request? | No. It only starts the workflows; review approval is separate. | | Can Copilot approve the runs itself? | No. The button is for a user with write access. | | Do branch protections and required checks still apply? | Yes. The agent is subject to them, so held runs leave required checks pending. | | Does it change what the agent may push? | No. It still pushes only to its single branch. | | Is it the same as the agent's own environment? | No. The agent's ephemeral environment runs on Actions separately; the hold concerns the repository's workflows triggered by its pushes. | ## A typical sequence 1. Copilot cloud agent finishes a session and pushes commits to its `copilot/` branch. 2. The repository's workflows are held; any required checks stay pending, so the pull request cannot satisfy them yet. 3. A reviewer with write access reads the diff and clicks **Approve and run workflows**. 4. The checks run. If one fails, the reviewer can mention `@copilot` with the failure, or use **Fix with Copilot** on the failing run, and Copilot starts a new session. 5. Copilot pushes again, and the new runs wait for approval again, because the hold applies to its pushes by default. 6. When the checks pass and a human approves, a human merges. The hold is one of several guardrails around the agent. It sits alongside the rule that the agent cannot mark its pull request ready for review, approve it or merge it, and alongside the firewall that limits its internet access while it works.

  • What stops a chain of Copilot automations from running workflows with nobody watching?
    The same hold. An issue or pull request opened by one automation could trigger another automation, but GitHub Actions workflows do not run on a Copilot pull request until a user with write access approves them, so the chain cannot execute workflows by itself. Automations also ignore events from users without write access unless you opt in.
  • Once you click Approve and run workflows, can Copilot cloud agent merge the pull request when the checks pass?
    No. Approving the runs only starts the workflows. Copilot cloud agent cannot mark its pull request ready for review, approve it or merge it; a human still has to review and merge, and the person who asked Copilot for the change cannot be the approving reviewer.

  • Actions is simply disabled for bot pushes, so there is nothing to approve.
  • Any repository reader can click Approve and run workflows on the pull request.
  • Turning off the approval only speeds things up and adds no risk.
  • Approving the workflow runs also approves Copilot's pull request.
  • Changes under .github/workflows/ are safe because Copilot cannot edit them.