Configuring Git Accounts

Before you begin

  • Create a new empty Git repository and make sure that you have read and write permissions. The name of the repository must be in the following format: RepoNameProject, where RepoName indicates the name of the repository and must start with an uppercase letter. Make sure that the repository name must be the same as the name that you are going to use for your new project.
    Note: The repository must not contain any files or commits before you link it to your project.
  • Create a personal access token for the Git account with access to the repository. Make sure that the repo scope is selected at a minimum. For detailed instructions on creating a personal access token, refer to the Git provider's documentation.
    Note: For Bitbucket, use an App Password instead, which can be created in the user's personal settings section.

Basic Flow

  1. Click Profile > Settings from the IBM® webMethods Integration title bar. A list of various settings applicable for the tenant appears.
  2. Click Version Control. The Version Control page appears, listing all existing Git accounts related to the logged in user.
    Note: Git accounts linked to projects before version 11.0.7 are considered shared and only Administrators can view and manage them. Users who want to commit changes to such a project are prompted to enter a Git username and access token when committing for the first time.
  3. In the Version Control page, click Add. The Add git account page appears.

  4. Provide the following details in the Add git account page.

    • Source Control - Account - Unique name for the account. The source control account name must only contain alphanumeric characters, underscores, and spaces. It cannot begin with a space and exceed 36 characters.
    • Username - Username used to access the Git server.
    • Hostname - Name of the Git server.
      Note: Do not add http:// or https:// in front of the host name. For example, for GitHub, enter github.com or github.enterprise.com, where enterprise is the name of your organization.
    • Personal Access Token - Personal access token for the Git account, and is applicable if you selected GitHub and Gitlab providers.
    • App Password - User-based access tokens for connecting with Bitbucket Cloud, and is applicable if you selected the Bitbucket provider.
  5. Click Validate and do one of the following steps:
    • If the Token Expiry Date field displays a date, verify that the date is when the personal access token expires. The date is provided in your Git repository.
    • If the Token Expiry Date field displays as No expiry, then the personal access token is valid for lifetime.

    If the validation is successful, the Add button is enabled.

  6. Click Add. The Git repository account is saved and listed in the Version Control page.
    Note: Click the corresponding Edit and Delete icons in the Action(s) column to modify or delete a Git account. You cannot delete an account that is linked to an existing project. To delete an account, you must first remove all projects that are linked to the account.