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: Refer to Azure DevOps documentation for information about user permissions.

​
Setup

1

Retrieve the repository's SSH URL

  1. In your browser, navigate to the Azure DevOps 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:
    • Git Provider - Select from the dropdown.
    • SSH URL - Copy and paste the repository’s SSH URL from Step 1.
    • Base Branch - Enter the name of the 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 an SSH public 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

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 setup, 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.