Skip to main content
When you submit a pull request (PR) to a GitHub branch that has been synced to a GitBook space, you can preview the content before merging. This allows you to check the impact of changes before merging them. You can use this feature to have a final layer of checks before merging a PR, allowing you to see your changes in a non-production environment before merging it into your synced branch. This behavior works out of the box, provided you have given the GitBook GitHub app the necessary read-only permissions to PRs. For every PR create using a target branch synced with a GitBook space, you’ll see a status added to the PR with a unique preview URL. Clicking the Details link on the status will take you to the preview URL for your content. You can then make sure the content is as expected before merging the PR.
Preview links are only accessible by users with a GitBook account.

​
Security considerations

For security reasons, by default GitBook doesn’t currently generate previews for PRs opened from forks of your repository. Because the content of the PR preview is accessible under your own domain, whether on .gitbook.io or your custom domain, a user could generate malicious content in a fork of your public repository and have it served under your name. We allow users to explicitly configure this through an option in the Git Sync settings.

​
FAQ

​
Why can’t I see a preview of my GitBook documentation in my pull request?

Common causes:
  • Your site isn’t published. PR preview URLs are served from your published docs site (on .gitbook.io or your custom domain).
  • Your site is behind authenticated access. Git Sync PR previews aren’t available for sites published behind authenticated access.

Build docs developers (and LLMs) love

Get started for freeTalk to us