GitHub Agent Merge comes to pull requests: Copilot watches a PR in the cloud and fixes failing Actions workflows and merge conflicts
Copilot now goes from writing code to getting the PR merged, and paid Copilot users can turn it on from the merge box.
// Key points
- Choose Watch and fix in the pull request merge box, then pick whether Copilot handles failing workflows, merge conflicts or both.
- When a selected blocker appears, Copilot fixes it in a cloud development environment; you can turn it on by default for all your PRs in Copilot settings.
- It combines with auto-merge so GitHub merges once all requirements pass; it is for paid Copilot plans, subject to organization and enterprise policies.
Builder's takeMaking CI green is the easiest thing for an agent to do badly: skipping tests or loosening assertions also turns it green. Before turning it on, make test and workflow files require human review through branch protection, enable it by default only for low-risk PRs like dependency bumps, and widen the scope after two weeks of reading its changes.
// Background · from #Coding agents
Full timeline →- Oct 31 Claude Code 2.1.314 adds a setting that blocks writes outside the working directories in every permission mode
- Oct 31 GitHub Actions workflow lockfiles are generally available: keep readable tag references while running only the locked commits, transitive dependencies included
- Oct 31 Copilot Automations can now be shared by a team: they belong to the repository, bill the repository's owner and keep running if the creator leaves