---
title: Configuring  DevOps Intelligence for GitHub, recent users
slug: configuring-devops-intelligence-for-github-recent-users
docTags: 
createdAt: 2026-07-09T18:45:09.160Z
---

This procedure is valid only for customers onboarded 6 June, 2024 or after. Procedures for legacy customers are provided in the subsequent section Configure  DevOps Intelligence for GitHub, legacy customers.

You must then onboard the technical service. Use the following procedures.

# Plan

1. Navigate to  DevOps Intelligence → **Settings & Utilities** → **Application Configurations**.
2. Select an existing application or create a new application.
3. Then **Add New Tools**→ **Plan** → **Add Tool Configuration**→ For tool engine select **GitHub**
4. Complete the configurations, categorized in the four tabs: **Release**, **Work Item Format**, **Bug Formats**, **Bug Severity**.
5. Click **Add Configuration**.

# Develop

1. Navigate to DevOps Intelligence → **Settings & Utilities** → **Application Configurations**.
2. Select an existing application or create a new application.
3. Then **Add New Tools**→ **Plan** → **Add Tool Configuration**→ For tool engine select **GitHub**
4. Select the pull request states.
5. Click **Add Configuration**.

# Secure

1. Navigate to  DevOps Intelligence → **Settings & Utilities** → **Application Configurations**.
2. Select an existing application or create a new application.
3. Then **Add Tools **→ **Secure** → **Add Tool Configuration**→ For secure categories select **Secure Alerts **→ for tool engine select **GitHub.**
4. Fill the configurations, categorized into two tabs (**Severity** and **State**).
5. Click **Add Configuration**.

:::hint{type="info"}
GitHub's Dependabot alert is used in the Secure phase, Secure Alerts category.
:::

# Onboard the technical service

You must now onboard the technical service. Use the following procedure:

1. Navigate to  DevOps Intelligence → **Settings & Utilities** → **Application Configurations**.
2. Click the overflow menu for the chosen application and click the **Onboard Technical Service** option.
3. Select the phase for which you want to configure GitHub. The page displays only the phases for which this tool has been configured for the application.
4. Select the tool engine as GitHub.
5. For **Connection**: Select the appropriate connection name from the drop down.

 DevOps Intelligence supports the following types of GitHub tracking:

- Organization
- Repository
- Non-Organization(Independent) Repositories

Use the following procedures:

# Organization Tracking

To track Organizational data, use the following procedure:

1. Select Tracking Type **Organization**.
2. Select the appropriate organization.
3. Click **Onboard** to onboard the technical service.

# Repository Tracking

To track repository level data, use the following procedure:

1. Select Tracking Type: **Repository**.
2. Select the appropriate organization for the repository. The organization accounts will be listed.
3. Select the appropriate repository. A search box allows filtering repositories by name. The selection of repos persists when the user navigates to the next page in the table.
4. Click **Onboard** to onboard the technical service.

:::hint{type="info"}
In case of GitHub Enterprise accounts, if the administrator has set a limit on API calls,  DevOps Intelligence  will optimize its data fetching process and will execute approximately 1000 calls each hour. This is to make sure no other task using the credentials is hampered. Once the limit is exceeded,  DevOps Intelligence  displays a message on GitHub`sync` page.
:::

# Non-Organization (Independent) Repositories

To track non-organization repositories, use the following procedure:

1. Select Tracking Type - **Repository**. (Optional)
2. Select the appropriate repository.
3. Click **Onboard** to onboard the technical service.

# Deleting the Technical Service

Use the following procedure to delete the technical service:

1. Navigate to  DevOps Intelligence  → **Settings & Utilities** → **Application Configurations**.
2. Expand the application to see all the associated phases.
3. Click on Overflow menu against the phase and click on **Delete Technical Service**.

##