Enabling GitLab Sync
In the space you want to sync with your GitLab repo, head to the space menu in the top right, and select synchronize with Git. From the provider list, select GitLab, and click configure.
Select GitLab as your Git provider
You can generate an API token in your GitLab user settings.
Ensure that you enable the following access for your token:
Enter your GitLab API access token to connect your GitLab account
Then you can paste the token into the API access token field when configuring your GitLab integration.
Select the repository you want to keep in sync with your GitBook content.
Can't see your repository? Ensure you've set the correct permissions when creating your API token.
Once you've selected the correct repository, choose which branch you want commits to be pushed to and synced from.
GitLab sync configuration
For many GitLab repositories, the
mainbranch might be automatically set to protected. If this is the case, we recommend adding a specific branch to sync your content between. You can then merge this into
mainand keep the protection in place.
When syncing for the first time, you'll have the option to sync in one of two directions:
- 1.GitBook -> GitLab will sync your space's content to the selected branch. This is great if you're starting from an empty repository and want to get your GitBook content in quickly.
- 2.GitLab -> GitBook will sync your space's content from the selected branch. This is great if you have existing markdown content in a repository and want to bring it into GitBook.
You're good to go. You'll notice that if your space was in live edit mode, it's now locked for live edits. This allows GitBook to reliably sync content to your repository when change requests are merged in GitBook, rather than the constant noise of trying to sync live edits!
When you edit on GitBook, every change request merge will result in a commit to your selected GitLab branch.
When you commit to GitLab, every commit will be synced to your GitBook space.