Skip to main content
Looking to use GitHub repositories as AI context? See the GitHub AI integration guide.
Using a git integration provides added development benefits of storing backups of model files and using pull requests to create collaborative and peer reviewed changes. Additionally, it’s possible to require pull requests, for those that want a more structured development lifecycle. Enabling the git integration requires the use of Branch Mode for modifications to the Shared model, ensuring a structured and organized development process.

​
Multiple models, one repository

Multiple Omni models can share the same git repository. When you connect additional models to a repository that’s already connected to another model, they’ll automatically share the repository’s deploy key and webhook configuration. This simplifies management and ensures consistent behavior across all models using the same repository. With Content in git, currently in beta, all models in a repository also share one omni/content/ folder for documents that require a pull request to publish.

​
Supported git providers

Omni’s git integration currently supports the following git providers:

Azure DevOps

Bitbucket Cloud

Bitbucket Data Center

GitHub

GitLab

​
Configuration

After a git repository is connected to a model, Organization Admins can configure the integration’s behavior by navigating to Model > Advanced > Git settings in the model IDE. For example, pull requests aren’t required by default. This can be changed using the integration’s settings. Refer to the git integration settings reference for more information.