---
metadata:
  - name: generator
    content: Diplodoc Platform v5.47.3
alternate:
  - https://yandex.com.tr/support/tracker/en/user/add-repository.md
title: "Integrating repositories with Yandex\_Tracker"
description: "This article lists the repositories you can add to Yandex\_Tracker."
---
> **Documentation Index:** Fetch the complete configuration index at https://yandex.com.tr/support/tracker/en/llms.txt


# Integration with repositories

In Yandex Tracker, you can set up integration with source code repositories on GitHub, GitLab, and Bitbucket to automatically display links to repository commits in Tracker issues.

To link commits to issues in Yandex Tracker:

1. Configure commit syncing between the repository and Yandex Tracker.

   Depending on your repository, choose one of the data sync methods:

   {% list tabs %}

   - Configuring a webhook in the repository

      The repository will send commit information to Yandex Tracker. This approach allows for faster data synchronization, so new commits will appear in the dedicated Yandex Tracker issue almost immediately.

      [How to configure a webhook in the repository](#webhook)

   - Configuring periodic repository polling

      Yandex Tracker will periodically poll the repository for commits.

      You can configure this sync method for repositories hosted online or deployed on your own server.

      - [How to configure Bitbucket repository polling](https://yandex.com.tr/support/tracker/en/user/bitbucket.md)
      - [How to configure GitHub repository polling](https://yandex.com.tr/support/tracker/en/user/github.md#poll)
      - [How to configure Gitab repository polling](https://yandex.com.tr/support/tracker/en/user/gitlab.md#poll)

   {% endlist %}

   {% note warning "" %}

   Syncing commits via a webhook configured in the repository is available only for GitHub and GitLab repositories hosted on your company’s servers.

   When polling a repository, links to commits may appear in Yandex Tracker with a delay of up to 10 hours.

   {% endnote %}

1. Enable commit display in the queue settings. This should be done in each queue where you need to display links to commits in issues.

    [How to enable commits in the queue](#link-commit)

1. <!-- source: en/_includes/add_commits.md -->
   To link a commit in the repository to an issue, specify the [issue key](*issuekey) in the commit comment. For example: `Fixing error TEST-123`.

   You can view the linked commits:

   * In the **Commits** tab on the issue page.
   * On the queue commits page. To switch to the commits page from the queue page, click <svg xmlns="http://www.w3.org/2000/svg" width="16" height="16" fill="currentColor" aria-hidden="true" class="yc-icon"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M14 6.125a1.874 1.874 0 1 1 .001 3.749A1.874 1.874 0 0 1 14 6.125zm-5.906 0a1.874 1.874 0 1 1 0 3.749 1.874 1.874 0 0 1 0-3.749zM2 6.125a1.874 1.874 0 1 1 .001 3.749A1.874 1.874 0 0 1 2 6.125z"/></svg></svg> → **Commits** in the top right corner.
   <!-- endsource: en/_includes/add_commits.md -->


## Configuring a webhook in the repository for syncing commits {#get-token}

To set up integration with Yandex Tracker, you need to configure a webhook in your repository to send new commit data to Tracker. To configure a webhook, first generate a URL and a token for the webhook in Yandex Tracker.

{% note warning "" %}

Synchronization via a webhook is available for GitHub and GitLab repositories hosted on your company’s servers.

Only a [Yandex Tracker administrator](https://yandex.com.tr/support/tracker/en/role-model.md) can add repositories.

{% endnote %}

1. <!-- source: en/_includes/repository-path.md -->
   In Yandex Tracker, in the left-hand panel, click <svg xmlns="http://www.w3.org/2000/svg" width="16" height="16" fill="currentColor" aria-hidden="true" class="yc-icon"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M14 6.125a1.874 1.874 0 1 1 .001 3.749A1.874 1.874 0 0 1 14 6.125zm-5.906 0a1.874 1.874 0 1 1 0 3.749 1.874 1.874 0 0 1 0-3.749zM2 6.125a1.874 1.874 0 1 1 .001 3.749A1.874 1.874 0 0 1 2 6.125z"/></svg></svg> → <svg xmlns="http://www.w3.org/2000/svg" width="18" height="18" fill="currentColor" aria-hidden="true" class="yc-icon nv-composite-bar__menu-icon"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 17 17"><path d="M15.84 4.69c-.06-.4-.37-.69-.75-.82-.4-.09-.8.04-1.06.29L12.2 6l-1.03-.16L11 4.81 12.84 3c.29-.28.38-.69.29-1.06-.13-.38-.41-.69-.82-.78a4.76 4.76 0 0 0-4.56 1.28A4.72 4.72 0 0 0 6.47 6.9L.72 12.62a2.66 2.66 0 0 0 0 3.63 2.58 2.58 0 0 0 3.62 0l5.72-5.72a4.8 4.8 0 0 0 5.78-5.84Zm-2.34 3.5a3.23 3.23 0 0 1-3.38.81l-.43-.16L3.3 15.2c-.37.4-1.1.4-1.47 0a1.04 1.04 0 0 1-.3-.75c0-.28.12-.53.3-.75l6.38-6.35-.13-.43a3.12 3.12 0 0 1 .72-3.41 3.2 3.2 0 0 1 2.31-1h.04L9.4 4.31l.46 2.82 2.82.5L14.5 5.8c0 .88-.34 1.75-1 2.38ZM2.72 13.75c-.28 0-.47.22-.47.5 0 .25.22.5.47.5.25 0 .47-.25.47-.5.03-.25-.19-.5-.47-.5Z"/></svg></svg> **Administration** and then open <svg xmlns="http://www.w3.org/2000/svg" width="14" height="14" fill="currentColor" aria-hidden="true" class="yc-icon page-admin__menu-icon"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 448 512"><path d="M224 48c97.167 0 176 27.723 176 61.714v4.571C400 148.277 321.167 176 224 176S48 148.277 48 114.286v-4.571C48 75.723 126.833 48 224 48m176 135.018v26.399c0 33.991-78.833 61.714-176 61.714S48 243.408 48 209.417v-26.399C85.813 210.982 155.021 224 224 224s138.187-13.018 176-40.982m0 96v26.834c0 33.991-78.833 61.714-176 61.714S48 339.842 48 305.851v-26.834C85.813 306.982 155.021 320 224 320s138.187-13.018 176-40.982m0 96v27.268C400 436.277 321.167 464 224 464S48 436.277 48 402.286v-27.268C85.813 402.982 155.021 416 224 416s138.187-13.018 176-40.982M224 0C137.052 0 0 23.26 0 109.714v292.571C0 488.758 137.03 512 224 512c86.948 0 224-23.26 224-109.714V109.714C448 23.242 310.97 0 224 0z"/></svg></svg> **Repositories**.
   <!-- endsource: en/_includes/repository-path.md -->

1. Click **Add** and select **Webhook**.

1. Choose **GitHub** or **GitLab** in the **Platform** field.

1. In the **Server address** field, enter the repository domain without protocol and full path. Click **Add**.

1. Wait for the URL and token to appear in the window. Copy and save these values: you'll need them to configure the repository.

    {% note warning "" %}

    You can copy the value of the token only once, after it's been created. You can always create a new token if you lose the original one, but then you'll need to update the webhook settings in the repository.

    {% endnote %}

1. Configure the webhook in your repository:

   * [How to configure a webhook on GitHub](https://yandex.com.tr/support/tracker/en/user/github.md#webhook)
   * [How to configure a webhook on GitLab](https://yandex.com.tr/support/tracker/en/user/gitlab.md#webhook)


## How to enable commit display in a queue {#link-commit}

<!-- source: en/_includes/add_commits.md -->
To see linked commits, enable this option in the queue settings:

1. <!-- source: en/_includes/transition-page.md -->
   In the left-hand panel, click <svg xmlns="http://www.w3.org/2000/svg" width="18" height="18" fill="currentColor" aria-hidden="true" class="yc-icon nv-composite-bar__menu-icon" viewBox="0 0 16 16"><path fill-rule="evenodd" d="M6.702 3.013 8 3.5V2.386A2 2 0 0 1 10.702.513l3.351 1.257A3 3 0 0 1 16 4.579v4.035a2 2 0 0 1-2.702 1.873L12 10v1.114a2 2 0 0 1-2.702 1.873L8 12.5v1.114a2 2 0 0 1-2.702 1.873L1.947 14.23A3 3 0 0 1 0 11.421V7.386a2 2 0 0 1 2.702-1.873L4 6V4.886a2 2 0 0 1 2.702-1.873ZM5.5 6.563l.553.207A3 3 0 0 1 8 9.579v1.319l1.824.684a.5.5 0 0 0 .676-.468V7.079a1.5 1.5 0 0 0-.973-1.405L6.176 4.418a.5.5 0 0 0-.676.468v1.676Zm4.553-2.293L9.5 4.062V2.386a.5.5 0 0 1 .676-.468l3.35 1.256c.586.22.974.78.974 1.405v4.035a.5.5 0 0 1-.676.468L12 8.398V7.079a3 3 0 0 0-1.947-2.809ZM1.5 11.421V7.386a.5.5 0 0 1 .676-.468l3.35 1.257c.586.219.974.779.974 1.404v4.035a.5.5 0 0 1-.676.468l-3.35-1.257a1.5 1.5 0 0 1-.974-1.404Z" clip-rule="evenodd"/></svg> **Queues** and select a queue. {#queue}
   <!-- endsource: en/_includes/transition-page.md -->

1. <!-- source: en/_includes/transition-page.md -->
   In the top right corner of the queue page, click <svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" fill="currentColor" aria-hidden="true" class="yc-icon nv-aside-header-footer-item__icon"><svg xmlns="http://www.w3.org/2000/svg" fill="none"><path fill="currentColor" fill-opacity=".85" fill-rule="evenodd" d="M8.875 2.125h2.25a.5.5 0 0 1 .5.5v.23c0 1.925 2.083 3.128 3.75 2.165l.2-.115a.5.5 0 0 1 .682.183l1.125 1.949a.5.5 0 0 1-.183.683l-.2.115c-1.666.962-1.666 3.368 0 4.33l.2.115a.5.5 0 0 1 .183.683l-1.125 1.949a.5.5 0 0 1-.683.183l-.199-.115c-1.667-.963-3.75.24-3.75 2.165v.23a.5.5 0 0 1-.5.5h-2.25a.5.5 0 0 1-.5-.5v-.23c0-1.925-2.083-3.128-3.75-2.165l-.2.115a.5.5 0 0 1-.683-.183l-1.125-1.949a.5.5 0 0 1 .183-.683l.2-.115c1.667-.962 1.667-3.368 0-4.33l-.2-.115a.5.5 0 0 1-.183-.683l1.125-1.949a.5.5 0 0 1 .683-.183l.2.115c1.667.963 3.75-.24 3.75-2.165v-.23a.5.5 0 0 1 .5-.5zm-2 .5a2 2 0 0 1 2-2h2.25a2 2 0 0 1 2 2v.23a1 1 0 0 0 1.5.866l.2-.115a2 2 0 0 1 2.731.732l1.125 1.949a2 2 0 0 1-.732 2.732l-.2.115a1 1 0 0 0 0 1.732l.2.115a2 2 0 0 1 .732 2.732l-1.125 1.949a2 2 0 0 1-2.732.732l-.199-.115a1 1 0 0 0-1.5.866v.23a2 2 0 0 1-2 2h-2.25a2 2 0 0 1-2-2v-.23a1 1 0 0 0-1.5-.866l-.2.115a2 2 0 0 1-2.732-.732l-1.125-1.949a2 2 0 0 1 .732-2.732l.2-.115a1 1 0 0 0 0-1.732l-.2-.115a2 2 0 0 1-.732-2.732l1.125-1.949a2 2 0 0 1 2.732-.732l.2.115a1 1 0 0 0 1.5-.866v-.23zM12.25 10a2.25 2.25 0 1 1-4.5 0 2.25 2.25 0 0 1 4.5 0zm1.5 0a3.75 3.75 0 1 1-7.5 0 3.75 3.75 0 0 1 7.5 0z" clip-rule="evenodd"/></svg></svg> **Queue settings**. {#settings}
   <!-- endsource: en/_includes/transition-page.md -->

1. Go to the **Integrations** tab.

1. Enable the option under **Commits**.
<!-- endsource: en/_includes/add_commits.md -->

[*issuekey]: An issue key is a unique identifier contained in the issue link. It consists of the queue key and a number, for example `TEST-123`.