Does assigning an issue on GitHub open a pull request?

Yes. GitHub's kick-off page says assigning an issue always creates a pull request. Starting from a prompt works on a branch by default, and you open the pull request when you are ready.

Do the checks run on their own?

Not by default on GitHub. GitHub's review page says that, by default, workflows will not run automatically when Copilot pushes. GitHub's changelog of March 13, 2026 says they wait until a person approves them, and that a repository administrator can skip that approval. You read the diff, especially workflow files, then you allow the workflows to run.

Home · Agents · 13 · Working with a coding agent

Concept card · Agents

Working with a coding agent

What this gets you. Hand a coding agent one change, and merge it only after the diff and the checks pass.

A coding agent is an AI tool, built on a language model, that reads your code, edits files on a branch, and can open a pull request for you to review before you merge.

Last checked 2026-10-20 6 min

Search for Working with a coding agent

What changed

Oct 20: First card. One change, from an issue that says when it is done to a merge by a person with write access.

1 What it is

A coding agent is an AI tool, built on a language model, that reads your code, edits files, and can run commands. You hand it one change as an issue, and you stay the one who merges. On GitHub, the changelog of April 1, 2026 calls this product Copilot cloud agent, formerly known as Copilot coding agent.

The steps, in order.

1 · IssueProblem, when it is done, files to change, files not to touch.
2 · BranchThe agent edits on its own branch.
3 · Pull requestAssigning the issue opens one. A prompt can stay on the branch until you open it.
4 · DiffYou read it before anyone merges.
5 · ChecksYour CI tests, or an eval you already trust. A miss stops the merge.
6 · MergeA person with write access merges.

Example: made up to show the idea.

A support assistant answers from sample docs. You want it to file a ticket.

Before. The issue says "Add ticket filing." The pull request changes 40 files, including the file that holds the API key setting.

After. The issue reads: "Add a ticket-filing tool to the support assistant. Done when the 8 saved eval cases still pass and 3 new cases each file a ticket. Change: ticket.js and ticket.test.js. Do not touch: settings/ or deploy files." The pull request changes 3 files. You ask about settings/api-key.js, the one file outside the issue. The agent pushes a fix. You let the checks run. They pass. A person with write access merges.

See the support assistant example.

What you do with the pull request

If the pull request	Then
passes its checks and stays inside the issue	Read the diff, then merge
passes its checks but touches files outside the issue	Ask, and hold the merge
edits a test so it passes	Do not merge it
is too big to review	Ask for a smaller pull request
touches secrets or deploy settings	Leave that file with the person who owns it
changes files under .github/workflows/	Read those files before you let the checks run

The workflow-file row follows GitHub's review page. The row about a test changed so it passes is your own check, the one on Evaluation basics.

2 Why it matters

Cost

Hand the agent one change, not a pile of them. A small change takes less time to review. GitHub's page on Copilot on GitHub.com says Copilot can work on one branch at a time and can open one pull request per task, and to break complex tasks into smaller, focused tasks. A second change is a second task.

Quality

The issue is the prompt, and it says when the change is done.

Write the issue like a prompt. GitHub's best-practices page says it is useful to think of the issue you assign to Copilot as a prompt, and that an ideal task includes complete acceptance criteria plus directions about which files need to be changed. OpenAI's prompting guide says a useful Codex prompt names the behavior you want, points to the relevant code or reproduction steps, preserves important constraints, and says how to verify the change.
Ask for a plan first. OpenAI's prompting guide says to enter /plan so Codex proposes an approach before editing. GitHub's changelog of April 1, 2026 says you can ask Copilot to produce an implementation plan and review the approach before Copilot writes any code.
Give it the project's rules in AGENTS.md. GitHub's changelog of August 28, 2025 says Copilot coding agent now supports AGENTS.md custom instructions. GitHub's best-practices page lists AGENTS.md for Copilot cloud agent, and Anthropic's Claude Code overview says Claude Code can read it in place of a CLAUDE.md.
Other tools do the same handoff. Claude Code, Cursor Agent, Copilot cloud agent, and Codex are examples. We're not paid by any maker. When we name a tool, it's there as an example, not an endorsement.

Risk

Passing checks are not a review. GitHub's page on Copilot on GitHub.com says logs do not replace your own review and testing. GitHub's review page says that, by default, GitHub Actions workflows will not run automatically when Copilot pushes changes to a pull request, and to be especially alert to proposed changes in the .github/workflows/ directory. Read those files, then allow the workflows to run. GitHub's changelog of March 13, 2026 says the workflows wait until a person approves them, that this stays the default, and that a repository administrator can skip that approval. If your repository requires approvals, that review page says your approval of a Copilot pull request won't count, and another reviewer must approve it. GitHub's kick-off page says Copilot receives the issue title, description, and existing comments at assignment time. Text you did not write is untrusted. See Prompt injection. GitHub's best-practices page lists production-critical issues and tasks involving security as ones you may choose to work on yourself. OpenAI's prompting guide says that for tasks delegated to the cloud, internet access is off during the agent phase unless you enable it for the environment.

3 How to apply · try today

Pick one small bug in a repository you can change. Write the issue with two lines that say when it is done, and one line that names the files not to touch. Compare it with the issue in the example above.

Common mistake

Merging because the checks pass when the diff also edits a file the issue did not name. GitHub's page on Copilot on GitHub.com says logs do not replace your own review and testing.

Self-check

Which issue is ready to hand to a coding agent?

Self-check

The pull request passes its checks, and the diff also edits the file that holds the API key setting. What do you do?

Questions

What is a coding agent?: A coding agent is an AI tool, built on a language model, that reads your code, edits files on a branch, and can open a pull request for you to review before you merge.
Does assigning an issue on GitHub open a pull request?: Yes. GitHub's kick-off page says assigning an issue always creates a pull request. Starting from a prompt works on a branch by default, and you open the pull request when you are ready.
Do the checks run on their own?: Not by default on GitHub. GitHub's review page says that, by default, workflows will not run automatically when Copilot pushes. GitHub's changelog of March 13, 2026 says they wait until a person approves them, and that a repository administrator can skip that approval. You read the diff, especially workflow files, then you allow the workflows to run.

Next: Production evaluation.