Connect your Git platform

The Git integration lets Packmind AI capture your coding practices from your latest Git repositories changes.

Connect your Git Platform Provider

To enable this feature, go to Settings -> Git Configuration. Select the space of your choice and select your Git Provider among the available ones (GitLab and GitHub).

BitBucket is planned for 2025, get in touch with us for more details.

Check below to configure the authentication with your selected Git provider.

Basically, Packmind will fetch the REST API of your Git providers to access to:

• The list of Git repositories

• The list of Pull/Merge requests and their metadata

• The list of discussions within each Pull/Merge request

• Accessing some file's raw contents for a given Git commit

This configuration is only for the selected space; however, you can use the same token as many times as you want. You may want to avoid this for providers like GitHub where the rate limit is set relative to the authenticated user.

If you need to perform IP Whitelisting operations on your self-hosted Git platform, check our public IP addresses here.

GitLab

Hostname

For this field, you must type your GitLab instance's hostname (usually a domain name). For example, gitlab.example.com or even an IP address such as 123.456.0.5:5555. By default, gitlab.com will be used for the requests.

Authentication token

The authentication token can be generated on GitLab as an Access Token, available for the following entities:

• Repositories (only allows a single repository)

• Projects (allows every repository in the project)

• Groups / Subgroups (allows every repository in the group / subgroup)

• Account (allows every repository on the account)

You can find the full list of tokens and how to create one here.

The minimum role required for the access token is Reporter (second lowest role), allowing access to the content of commits (to be displayed on Packmind).

Likewise, the read_api scope is required, as the read_repository scope does not allow for project discovery (to link repositories).

GitLab | Project > Settings > Access Tokens

GitHub

Hostname

For this field, you must type the hostname (usually a domain name) of your GitHub instance's API, such as github-api.example.com or even an IP address such as 123.456.0.5:5555. By default, api.github.com it will be used for the requests.

Authentication token

The authentication token can be generated on GitHub as a Personal access token, preferably as a Fine-grained token. Refer to this page to learn how to create one.

Organizations may require you to approve a Personal access token before being able to use it on its repositories. Read more here.

This token will require the following permissions:

• Contents

• Metadata

• Discussions

• Pull Requests

Azure DevOps

Hostname

For this field, you must type the hostname (usually a domain name) of your Azure DevOps instance's API, such as dev.azure.example.com or even an IP address such as 123.456.0.5:5555. By default, dev.azure.com it will be used for the requests.

Organization

The name of your Azure DevOps organization is mandatory. You can find it next to the Azure DevOps logo, top left of the app :

In this example, promyze-internal is the organization name

Authentication Token

The authentication token can be generated as a Personal Access Token (PAT). More information on how to create a PAT here. The token will require the following permission :

• Code: Read

Link Git Repositories to spaces

Once the authentication is valid, you can search for repositories through the Git repositories selection field, with a limit next to the list of repositories. Once the Git repositories are configured, you can now run extractions from the Inbox.

How to create coding practices