A pull request can be ready for review and lose that status minutes later when its base changes or a test fails. GitHub is bringing Copilot into that gap between finishing a change and integrating it: Agent Merge is now available directly in pull requests, following its October 28 announcement.
Developers choose which blockers the agent should watch. When one appears, Copilot starts working on a fix. That can reduce maintenance work, while leaving the team responsible for judging the code that eventually lands.
Fixing a blocker and merging are separate choices
The Watch and fix option covers failing GitHub Actions workflows, conflicts with the target branch, or both. It requires a paid plan and compatible organizational policies. The operational documentation also requires the Enable automations policy and excludes forked and stacked pull requests.
Enabling Agent Merge does not enable auto-merge. The name may suggest broader authority than the feature actually grants. Copilot can prepare fixes and keep a PR clear of blockers; automatic integration is a separate configuration that remains subject to repository requirements.
A team that requires human approval can therefore consider automated maintenance without changing that rule. It still needs a clear owner for reviewing changes made after the initial version.
A green check must retain its meaning
Consider a hypothetical API change that breaks a test. The test might be outdated, or the implementation might have broken required behavior. Either explanation could lead to a small patch, but they call for very different decisions.
A useful fix does more than remove a red indicator. Reviewers need to establish whether it preserves the expected behavior. Deleting an assertion may make the run pass while removing the evidence that protected the system.
Conflicts carry a similar risk. Two changes may compile together while expressing incompatible business rules. Automation can help reconstruct context, but evaluating their combined effect still matters.
The person enabling it should also watch usage
The documentation charges AI credits to the person who enables monitoring, who may not be the PR author. It also explains that fixes run in a GitHub Actions-based development environment using repository customizations.
Before enabling the feature by default, a small sample of PRs can reveal which blockers occur, which files get changed and how much review the fixes require. The useful comparison is time to a reviewed, correct change, rather than time to the next green check.
Sources: GitHub announcement and Agent Merge documentation.