Skip to main content
Multiple Omni models can share the same git repository. If you’re connecting a model to a repository that’s already connected to another model, you only need to complete the Omni-side setup—the repository’s deploy key and webhooks are already configured.

​
Requirements

To follow the steps in this guide, you’ll need:
  • Omni Connection Admin permissions for the model you want to connect to git
  • An existing git repository in GitHub, GitLab, Bitbucket, or Azure DevOps
  • Permissions in your git provider that allow you to:
    • Add webhooks to repositories
    • Add deploy/SSH keys to repositories
    Refer to the documentation for your git provider for information about their user permissions.

​
Setup

1

Retrieve the repository's SSH URL

  1. In your browser, navigate to the GitHub git repository you want to connect to Omni.
  2. Click the Code button.
  3. In the modal that displays, locate the SSH option.
Keep this page open - you’ll need it in the next step.
  1. In your browser, navigate to the GitLab git repository you want to connect to Omni.
  2. Click the Code button.
  3. In the modal that displays, locate the SSH option.
Keep this page open - you’ll need it in the next step.
  1. In your browser, navigate to the Bitbucket git repository you want to connect to Omni.
  2. Click the Clone button near the top right corner of the page.
  3. In the modal that displays, click the HTTPS dropdown, then select SSH.
Keep this page open - you’ll need it in the next step.
  1. In your browser, navigate to the Azure DevOps git repository you want to connect to Omni.
  2. Click the Clone button near the top right corner of the page.
  3. Click the SSH option to display the repository’s SSH URL.
Keep this page open - you’ll need it in the next step.
2

Connect the repository to Omni

  1. In Omni, click Develop.
  2. Click the model you want to connect to git.
  3. In the model IDE, click Model > Git settings.
  4. You’ll be prompted to enter connection details for the repository:
    • SSH URL - Copy and paste the repository’s SSH URL from Step 1
    • Base Branch - Enter the name of default branch for the repository. Omni will default to main unless a different name is specified.
  5. Click Configure Git.
The page will update to display additional git settings, along with information for deploy keys and webhooks.
Connecting to a repository that’s already linked to another Omni model? Skip to Step 5 - the deploy key and webhooks are already configured.
3

Add a repository deploy key

Using Bitbucket? The steps for adding a repository deploy differ between self-hosted and Cloud Bitbucket instances. Make sure you click the correct Bitbucket type form the options below.
  1. In the GitHub repository, click the Settings tab.
  2. Click Deploy keys, located in the Security section of the left navigation.
  3. Click Add deploy key.
  4. Fill in the fields as follows:
    • Title - Enter a descriptive title to help you identify what the key is used for. For example, Omni Snowflake Model
    • Key - Copy the Public key from the Omni Git settings page and paste it into this field.
    • Allow write access - Check this box, which will allow Omni to push changes made in Omni to the repository
  5. Click Add key.
  1. Create a project deploy key for the GitLab repository by following GitLab’s documentation.
  2. Fill in the deploy key fields as follows:
    • Title - Enter a descriptive title to help you identify what the key is used for. For example, Omni Snowflake Model
    • Key - Copy the Public key from the Omni Git settings page and paste it into this field.
    • Grant write permissions to this key - Check this box, which will allow Omni to push changes made in Omni to the repository
  3. Click Add key.
Bitbucket Cloud access keys are read-only. To allow Omni to push changes, you’ll need to add the SSH key to a user account with write access to the repository. We recommend using a service account for this purpose.
  1. Create a service account with write access to the repository.
  2. In the service account, navigate to Personal Bitbucket settings > SSH keys.
  3. Click Add key.
  4. Fill in the fields as follows:
  • Label - Give your new SSH key a descriptive label
  • Key - Copy and paste the public key from the Omni git settings page into this field
  1. Click Add key to save the key.
  1. In the Bitbucket repository, click Repository settings.
  2. Click Access keys, located in the left navigation.
  3. Click Add key.
  4. Fill in the fields as follows:
    • Key - Copy the Public key from the Omni Git settings page and paste it into this field.
    • Permission - Select Write to allow Omni to push changes made in Omni to the repository
  5. Click Add key.
  1. Browse to the Azure DevOps web portal (ex: https://dev.azure.com/<your-org-name>/).
  2. Click the User settings icon next to your avatar in the top right corner of the page.
  3. Click SSH public keys.
  4. On the page that displays, click + New Key.
  5. In the Add New SSH Key panel that displays, fill in the following:
    • Name - Enter a descriptive name, such as Omni Snowflake Model
    • Public Key Data - Copy and paste the Public key from the Omni Git settings page
  6. Click Add.
4

Add repository webhooks

  1. The repository settings page should still be open in GitHub. If not, re-open it.
  2. Click Webhooks, located in the Code and automation section of the left navigation.
  3. Click Add webhook.
  4. Fill in the fields as follows:
    • Payload URL - From the Omni Git settings page, copy the Payload URL and paste it into this field.
    • Content type - Select the application/json option.
    • Secret - From the Omni Git settings page, copy the Webhook secret and paste it into this field.
  5. In the Which events would you like to trigger this webhook? section:
    1. Click Let me select individual events.
    2. Select the Pull request event.
    3. If the Push event is selected, deselect it.
  6. When finished, click Add webhook.
  1. The repository settings page should still be open in GitLab. If not, re-open it.
  2. Click Webhooks.
  3. Click Add new webhook.
  4. Fill in the fields as follows:
    • URL - From the Omni Git settings page, copy the Payload URL and paste it into this field.
    • Secret token - From the Omni Git settings page, copy the Webhook secret and paste it into this field.
  5. In the Custom headers section:
    1. Click Add custom header.
    2. In the Header name field, enter Content_type.
    3. In the Header value field, enter application/json.
  6. In the Trigger section, select Merge request events.
  7. When finished, click Add webhook.
  1. If the repository settings page isn’t still open, open it by clicking Repository settings in the left navigation.
  2. Click Webhooks, located in the Workflow section of the left navigation.
  3. Click Add webhook.
  4. Fill in the fields as follows:
    • Title - Enter a descriptive title, such as Omni Pull Request Webhook
    • URL - From the Omni Git settings page, copy the Payload URL and paste it into this field.
    • Secret - From the Omni Git settings page, copy the Webhook secret and paste it into this field.
  5. In the Triggers section, select Choose from a full list of triggers.
  6. Select only the Pull Request events:
    • Pull Request Created
    • Pull Request Updated
    • Pull Request Merged
  7. When finished, click Save.
Next, you’ll create three webhook subscriptions for the Azure DevOps repository, one for each of the following event types:
  • Pull request created
  • Pull request updated
  • Repository status updated
1

Create the webhook subscription

  1. Navigate to the Azure DevOps project that contains the repository you want to connect to Omni.
  2. Click Project settings.
  3. Click Service hooks, located in the General section of the left navigation.
  4. On the Service Hooks page, click the + icon or Create subscription.
  5. On the Service screen, click Web Hooks and then Next.
2

Configure the Trigger

  1. On the Trigger screen, select one of the following for the Trigger on this type of event field.
    1. Pull request created
    2. Pull request updated
    3. Repository status updated
  2. Select the Repository you want to connect to Omni.
  3. If the Target branch field displays, select the main branch.
  4. When finished, click Next.
3

Configure the Action

On the Action screen, fill in the fields as follows:
  • URL - Copy and paste the Webhook URL from the Omni Git settings page
  • Basic auth username - omni
  • Basic auth password - Copy and paste the Webhook secret from the Omni Git settings page
  • HTTP headers - The value of this field depends on the type of event being configured:
    • Pull request created - x-azuredevops-omni-event:created
    • Pull request updated - x-azuredevops-omni-event:update-push
    • Repository status updated - x-azuredevops-omni-event:update-status
When finished, click Finish to create the webhook.
4

Repeat steps 1-3

Repeat these steps for each of the three webhook subscription types.
5

Test the connection

To verify the set up, navigate back to the Git settings page in Omni. Click the Test git connection button near the top of the page to test the connection.

​
What’s next?

After the setup is complete, you can configure the integration’s behavior by changing its settings. Refer to the git integration settings reference for more information.