Generating a Git access token for asset promotion

If you plan to use GitHub or GitLab to manage assets across instances of IBM® Software Hub, you must generate a Git access token.

Who needs to complete this task?

Any users who need to manage assets across instances by using Git must complete this task.

When do you need to complete this task?

You must complete this task before you can push changes to or pull changes from Git.

In addition, you must complete this task if your access token expires or is revoked.

About this task

You can use one of the following Git providers:

  • GitHub
  • GitHub Enterprise
  • GitLab
  • GitLab Self-Managed

Procedure

Generate a personal access token:

The permissions that are associated with your token depend on your Git provider:

GitHub and GitHub Enterprise

Create a new personal access token from the Settings > Developer Settings page.

The permissions depend on the type of token that you generate:

Classic token
The token must have the repo scope.
Fine-grained token
The token must have Read and write permissions on the repository contents:
  1. Select the resource owner of the repository.
  2. Select the repository that you want to create the token for.
  3. Under Repository permissions > Contents, select Read and write access.
GitLab and GitLab Self-Managed

Create a new personal access token from the User Settings > Personal access tokens page.

The token must have the following permissions:
  • read_user
  • read_repository
  • write_repository