Skip to main content

Configuring Git credentials

Admin prerequisite

Before you can configure your personal Git token, an administrator must have set up the Git provider integration in Witboost. Admins configure this at Administration > Configuration > Platform > Git Tokens by adding the provider host and a read-only service token. For Azure DevOps, the administrator also defines the organizations available to users. If you get an error stating that no Git integration is configured for your host, reach out to your platform admin.

When performing actions that will act on a repository (creating a new repository, committing/pushing some files, etc) witboost requires you to specify the token that you will be using to interact with the git repository.

Unless your organization is using a common access token for every user (not recommended), if your personal access token is not set in your account settings, an error message will notify you to configure it in your settings.

To do so, from any page in witboost:

  1. On top of the page, click on your profile picture and then click on Settings and Profile
  2. In the Settings page click on the Advanced tab
  3. Insert your token for your Git provider. The token is stored securely and cannot be viewed after it is saved.
Azure DevOps

Git configuration displays one organization-scoped token field for each organization configured by your administrator. Add the PAT created for the corresponding organization. You cannot add or rename organizations from your settings.

The Global token (legacy) field is used only when an organization-scoped token is not set. Existing global tokens continue to work, but organization-scoped PATs are recommended because Azure DevOps may no longer support global PATs.

You can always come back and delete it if you need to add a new one.

Generating Access Tokens in your Git Provider​

As mentioned before, Witboost will store all the components information in your git provider. For this reason, we need to generate an Access Token to allow the platform to create the repositories and commit information in them.

Below you will find official documentation websites to know how to generate access tokens in your configured git provider:

Be sure to create a token with the following scopes:

  • api
  • read_repository
  • write_repository
  • read_api

Official Gitlab documentation: link