# Git Connector - Azure DevOps
With the integration of Git, repository management becomes highly practical and efficient. We currently support integration with Azure DevOps. Whether you're merging branches, tracking changes, or rolling back to previous versions, you can track all these changes seamlessly within your Jira instance. This integration lets you easily track **repositories**, **branches**, **commits**, and **pull requests**.
Our Git integration app for Jira is available at the following link: [Git Connector for Jira.](https://marketplace.atlassian.com/apps/1236406/git-connector-for-jira-azure-devops-github-gitlab?hosting=cloud\&tab=overview)
{% hint style="warning" %}
While it is possible to create a Git integration using the Azure DevOps integration app, it is mandatory to have the Git Connector app installed.
{% endhint %}
### How to Build a Git Integration for Azure DevOps
#### 1. Launch the Getint App:
* Navigate to **Apps**, launch the app **Git Connector for Jira**, go to **Integrations**, click **Create Integration**, and select **Sync GIT Repository**.
* If you’re using Getint On-Premise, simply launch the app, click **Create Integration**, and select **GIT**.
#### 2. Create a Connection with Azure DevOps:
* Click the **Connect App** button, and select **Azure DevOps**.
* Create a connection or select an existing one.
* Tap on **Create a new connection** if you don’t have an existing one.
* Enter your instance URL, and click on **Connect**.
* Name the connection, input your email, and paste the token generated (create the personal access token following the instructions in this guide: [Connections](https://docs.getint.io/guides/quickstart/connection#azure-devops)). Then click **Add**.
* Once you've added your details, you'll find your new connection in the dropdown list of available connections. Please select it and click **Connect** to complete the process.
{% hint style="warning" %}
For Git Azure DevOps integrations, it is important to set the scope **Code** to **Read**. Otherwise, you’ll get the following error:
*Unfortunately, your integration failed to save due to the following reason: Forbidden.*
{% endhint %}
#### 3. Establish a Connection with Jira:
* Ensure that you are logged in with administrative rights, then click on **Connect App** and select **Jira**. Click on **Create New** to set up a new connection with your Jira instance and enter the URL of your Jira instance.
* Unlike **Continuous Syncs** or **Migrations**, GIT integrations require users to set up OAuth in your Jira instance. Please ensure you have admin permissions; otherwise, you will not be able to set up the OAuth credentials. Then, follow our guide to configure a Jira OAuth at the following: [Connection | Jira OAuth.](https://docs.getint.io/guides/quickstart/connection#jira-cloud-oauth)
* Enter the necessary details to establish the connection.
* After entering your details, your new connection will appear in the dropdown list of available connections. Please select it and click **Connect** to finalize the setup.
#### 4. Building Your Integration:
* By default, the Git repositories will synchronize with all projects in your Jira instance. However, if you uncheck this option, you can choose one or multiple projects where you want this information to be accessible.
* For instance, you can choose specific projects according to your company's requirements. Then, select the Git repositories you wish to synchronize. Lastly, give your integration a name and click **Create** at the top right corner of the screen to save it.
* After creating your integration, it will be readily available in the Integrations section within Workflows, identified by a code icon.
* If you did not install the Git Connector app as instructed at the beginning of the article, you will encounter an error like the one shown below:
#### 5. Test the Integration and Sync Your Branches
* To start syncing branches, use the Jira task ID as a prefix for the branch, commit, and pull request names. For branch names, only underscores or dashes can be used instead of spaces. For example **ED-32\_Energy\_Dot**.
* For instance, if you are syncing an item with the Jira ID **ED-32**, your branch should be named **ED-32** followed by the branch name, as shown below:
Example of proper branch naming for synchronization.
* If you fail to use the correct naming prefix to sync your items, you will encounter an error similar to the one shown below:
* The Git repository details of your Jira items will be available in the Development field. Refresh the page if you don’t see any changes to the Development field.
{% hint style="warning" %}
Depending on your Project template, the Development field may not be visible. In such cases, you must either add the field by modifying the issue layout or switch to a different template.
{% endhint %}
* Clicking on this field allows you to effortlessly access all the information being fetched from the repositories.
{% hint style="info" %}
Getint enables the synchronization of Repositories, Branches, Commits, and Pull Requests. However, please note that changes cannot be submitted from Jira to the Git repository. The synchronization of repository information is one-way from Azure DevOps.
{% endhint %}
### Conclusion
By following this detailed guide, you can effortlessly integrate Azure DevOps repositories with Jira and fully leverage efficient repository management. Should you need any assistance or have additional questions, please feel free to contact us here.
