July 23, 2026 - Git Sync allows technical teams to synchronize GitHub or GitLab repositories with GitBook and turn Markdown files into beautiful, user-friendly docs.

Git Sync lets your teams update your docs in our visual editor or in code — with everything staying perfectly in sync. Set up a two-way sync between GitBook and a GitHub or GitLab repo to create a docs-as-code workflow that works for everyone.

July 27, 2026 - Follow the instructions in the GitHub popover and either give GitBook specific repository permissions, or allow access to all repositories, depending on your needs. Select the account and repository you want to keep in sync with your GitBook content.

February 12, 2026 - GitBook → repository: Export your space content to the selected branch. ... Click Sync to start the initial sync. After it finishes, Git Sync keeps GitBook and your repository synchronized in both directions.

January 10, 2025 - Git Sync allows technical teams to synchronize GitHub or GitLab repositories with GitBook and turn Markdown files into beautiful, user-friendly docs.

April 20, 2026 - Because Git Sync links your documentation to a GitHub or GitLab repository, you can make changes from your code editor and they’ll automatically sync to your docs when you merge.

GitHub Sync allows technical teams to synchronize GitHub repositories with GitBook and turn Markdown files into beautiful, user-friendly docs.

If your repository has markdown content that uses -, GitBook will change that to * during the synchronization that happens from GitBook to GitHub.

December 17, 2024 - In GitBook, select the repository and branch you want to sync, choose the direction of the initial sync, and GitBook will do the rest. Finally, you can start your initial sync. When syncing for the first time, you’ll have the option to sync ...

Git Sync allows technical teams to synchronize GitHub or GitLab repositories with GitBook and turn Markdown files into beautiful, user-friendly docs.

July 27, 2026 - Make sure that you have installed the GitBook GitHub app to the correct locations (when installing the app, you can choose to install it to your personal GitHub, or to any organization you have permissions for) and that you have given the app the correct repository permissions. Make sure that your access token has been configured with the following access: ... If your repository does not include a SUMMARY.md file, GitBook will automatically create one upon the first sync.

To begin the GitSync setup process, access the GitSync configuration panel. You can do this either by clicking on the tray at the bottom of your document or through the menu icon located in the upper right corner of your GitBook AI interface.

March 10, 2026 - You can then merge this into main and keep the protection in place. When syncing for the first time, you’ll have the option to sync in one of two directions: GitBook -> GitLab will sync your section’s content to the selected branch.

June 10, 2026 - Path-based configuration only applies inside that section’s synced scope. It doesn’t make sibling directories or repository-level folders available to other sections automatically. For multi-section repository setups, see Monorepos. ... The value of those properties is a path to the corresponding files. The path is relative to the “root” option. For example, here’s how you can tell GitBook to look into a ./product folder for the first page and summary: When Git Sync is enabled, remember not to create or modify readme files through GitBook's UI.

When syncing for the first time, you’ll have the option to sync in one of two directions: GitBook -> GitHub will sync your space’s content to the selected branch.

In GitBook, select the repository and branch you want to sync, choose the direction of the initial sync, and GitBook will do the rest. Finally, you can start your initial sync. When syncing for the first time, you’ll have the option to sync ...

Git Sync status shows an unexpected error​GitBook is not using my docs folderGitBook is creating new markdown files​Nothing happens on GitBook after adding a new file to my repositoryMy table of contents is not correctly structuredError when pushing to the repository with protected branchGit ...

January 6, 2026 - Once set up, it keeps all your content synchronized between the GitBook app and your codebase. Git Sync is bi-directional, so changes you make in GitBook’s visual editor are automatically synced — as are any commits made on GitHub or GitLab.