Back to rankings

GitHub Copilot App: Set Up Agent Merge Directly from a Pull Request

GitHub CopilotView original changelog

The GitHub Copilot app now lets developers set up Agent Merge from a pull request so Copilot merges it once it is ready. Agent Merge stays enabled while required checks or rules are still pending, instead of giving up early.

Key Takeaways

  • Agent Merge can now be set up directly from a pull request in the GitHub Copilot app.
  • Copilot merges the pull request automatically once it is ready.
  • Agent Merge stays enabled while required checks or rules are pending, so it does not stall.
  • It reduces the manual check-back loop at the end of a pull request.
  • It keeps the session-to-merge lifecycle in one app.
  • It arrived in the weekly releases for November 2.

Hand Off the Last Mile of a Pull Request

The GitHub Copilot app added the ability to set up Agent Merge straight from a pull request. Once enabled, Copilot takes over the final stretch and merges the pull request when it is ready, so developers no longer need to return to it repeatedly to check whether approvals and checks have landed.

Patience While Checks Are Pending

Agent Merge stays enabled while required checks or rules are still pending. That means a pull request waiting on continuous integration or a branch protection rule does not drop out of the flow. Copilot continues to wait and completes the merge once the conditions are satisfied.

Why It Matters

For teams that open many pull requests with agent sessions, merging is often the step that gets forgotten or delayed. Configuring it from the pull request itself in the app keeps the whole lifecycle, from session to merge, in one place. The feature appeared in the GitHub Copilot weekly releases for the week of November 2.

Copilot App: Set Up Agent Merge from a Pull Request | Yet Another Changelog