Connect your Git platform

Find out how to let Packmind AI capture your coding practices from your latest Git repositories changes.

Connect your Git Platform Provider

You must be a Driver or an Administrator in your current space to access this page and update the configuration.

To enable this feature, click on your username/avatar in the top right corner and go to Administration -> Git Configuration. Select the space of your choice and select your Git Provider among the available ones (Gitlab, GitHub, Azure DevOps, or BitBucket).

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

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.

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

Bitbucket

Hostname

For this field, you must type your Bitbucket instance's API hostname (usually a domain name; The hostname bitbucket.com by itself will not work). For example, bitbucket-api.example.com or even an IP address such as 123.456.0.5:5555. By default, api.bitbucket.com will be used for the requests.

Authentication token

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

• Repositories (only allows a single repository)

• Projects (allows every repository in the project)

• Workspaces (allows every repository of the workspace)

You can find some information on how to create one here.

On the SaaS version of Bitbucket (bitbucket.org), access tokens for Projects and Workspaces are a Premium feature, leaving only Repositories access tokens for free.

This token will require the Repositories (Read) scope, necessary to discover repositories and read the content of their commits. Read more about scopes here.

Bitbucket | Repository > Settings > Access tokens

Azure DevOps

Hostname

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

Organization

For this field, simply type the organization from which you wish to select repositories.

Project

You can restrict the scope to a specific project to limit the number of fetched repositories. You might need to click on "Save" and refresh the page to get a new list of repositories.

Authentication token

The authentication token can be generated on Azure DevOps as a Personal access token. Refer to this page to learn how to create one. This token will require the Code (Read) scope to discover projects and repositories, and read the content of their commits.

Azure DevOps | User settings > Personal access tokens

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.

The changes will not be applied as long as the Save button is not pressed.

Once the Git repositores are configured, you can now run extractions from the Inbox.

How to create coding practices