> For the complete documentation index, see [llms.txt](https://gitbook-open-v2-preview.gitbook.workers.dev/url/gitbook.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook-open-v2-preview.gitbook.workers.dev/url/gitbook.com/docs/docs-as-code/git-sync.md). # GitHub & GitLab Sync Synchronize your GitBook docs with GitHub or GitLab with GitBook’s bi-directional integration
A GitBook screenshot showing the Git Sync setup

Set up Git Sync for your GitBook docs.

### Overview Git Sync allows technical teams to sync GitHub or GitLab repositories with GitBook and turn a repo of Markdown files into beautiful, user-friendly docs. Edit directly in GitBook’s powerful editor while keeping content synchronized with your codebase on GitHub or GitLab. Git Sync is bi-directional, so changes you make directly in GitBook’s editor are automatically synced, as are any commits made on GitHub or GitLab. This allows developers to commit directly from GitHub or GitLab and technical writers, instructional designers, and product managers to edit, discuss and feedback changes directly in GitBook. ### Set up Git Sync

:github:

Set up GitHub Sync

Set up and authorize the GitHub integration for GitBook.Enabling GitHub Sync

:gitlab:

Set up GitLab Sync

Set up and authorize the GitLab integration for GitBook.Enabling GitLab Sync
{% hint style="info" %} Git Sync supports IP allowlisting for Enterprise customers. If your GitHub, GitLab, or internal network only accepts traffic from approved IPs, allowlist these outbound Git Sync IPs before you enable the integration: * `34.136.22.210` * `34.29.189.57` * `35.223.181.150` * `34.72.115.112` * `136.116.236.109` {% endhint %} {% hint style="info" %} Only [administrators and creators](/url/gitbook.com/docs/collaborate/member-management/roles.md) can enable and configure Git Sync. {% endhint %} ### Working with AI Agents When working on your docs locally with Git Sync, you can use GitBook's [skill.md file](/url/gitbook.com/docs/docs-as-code/ai-coding-assistants-and-skillmd.md) to provide an AI coding assistant with context about GitBook's blocks, features, and best practices. Head to [Agent skills](/url/gitbook.com/docs/docs-as-code/ai-coding-assistants-and-skillmd.md) to learn more. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://gitbook-open-v2-preview.gitbook.workers.dev/url/gitbook.com/docs/docs-as-code/git-sync.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.