Review and merge a Pull Request

Last modified: June 3rd, 2026

Permissions required

Members of the Editors and Technical Editors Default Permission Groups, or Custom Permission Groups with the site:publish:write permission, can merge a Pull Request from CloudCannon. Additional restrictions configured on your Git Provider may also apply.

When a Team Member publishes from a branched Site configured with the Pull Request Publishing Method, CloudCannon opens a Pull Request on your Git Provider. Reviewing the Pull Request, including viewing the diff, leaving comments, and approving, happens on your Git Provider, not in CloudCannon.

For more information about Publishing Methods, please read our documentation on what Publishing Methods are.

To review a Pull Request, open it on your Git Provider (GitHub, GitLab, or Bitbucket) using your Git Provider's review tools. From CloudCannon, you can navigate to a Pull Request in two places:

  • The Pull Requests tab on your Project, which lists all open Pull Requests in the connected Git Repository.
  • The Publishing page of a branched Site with an open Pull Request, which shows the Pull Request title, description, and changes.
A screenshot of the Publishing page on a Site with an open Pull Request shows the Pull Request details and buttons to Publish or Close the Pull Request.

Once a Pull Request is approved on your Git Provider, you can merge it from your Git Provider or from CloudCannon. To merge from CloudCannon, click the Publish pull request button on the branched Site's Publishing page. If your Git Provider has additional restrictions on the branch, CloudCannon will return an error when those restrictions are not met.

If you close the Pull Request — either on your Git Provider or by clicking Close pull request on the Publishing page — the branched Site will retain its saved changes until a Team Member updates the content or deletes the Site.

Related Resources

Open in a new tab