Skip to main content
Version: ACE 5

Connecting to GIT

Getting GIT provider access​

note

For GitLab, repository url must end with .git. Eg: https://gitlab.com/someuser/some-repo-name.git

ACE uses git repository as a store for workspaces and git provider needs to be configured. Supported GIT providers include Azure, Bitbucket, Gitlab, GitHub and more.

This section provides step-by-step instructions to create a Git access token with read & write permissions for most popular Git providers.

GitHub

Classic Personal Access Token (PAT)

  1. Navigate to GitHub Personal Access Tokens.
  2. Click Generate new token (classic).
  3. Provide a note to identify the token.
  4. Set expiration (recommended for security).
  5. Select the required scopes:
    • repo (Full control of private repositories, includes read & write access)
  6. Click Generate token and copy it immediately.

Fine-Grained Personal Access Token (FGPAT)

  1. Navigate to GitHub Fine-Grained Tokens.
  2. Click Generate new token.
  3. Provide a name and expiration (recommended for security).
  4. Select repository access:
    • Choose specific repositories which are necessary for ACE
    • Set repository permissions to:
      • Read and Write for Contents.
  5. Click Generate token and copy it immediately.
Azure DevOps
  1. Navigate to Azure DevOps Personal Access Tokens.
  2. Click on User settings (top-right) > Personal access tokens.
  3. Click + New Token.
  4. Provide a name and expiration date.
  5. Select Organization (if applicable).
  6. Set Scopes:
    • Code (Read & Write)
  7. Click Create and copy the token immediately.
Bitbucket
  1. Navigate to Bitbucket App Passwords.
  2. Click Create App Password.
  3. Provide a label for the token.
  4. Set permissions:
    • Repositories: Read, Write
  5. Click Create and copy the token immediately.
GitLab
  1. Navigate to GitLab Access Tokens.
  2. Click Add new token.
  3. Provide a name and expiration date.
  4. Set Scopes:
    • read_repository
    • write_repository
  5. Click Create personal access token and copy it immediately.

See more detailed official documentation on how to create a personal access token for each provider:

Open ACE settings​

Once the repository URL, access rights and initial repository branch are prepared ACE can be connected to git.

Settings menu

Settings cog

Specify repository settings​

Available settings are:

  • Repository URL, username and token
  • Default branch - This branch is used as the base for any new branches created in ACE. If no branches exist create one using git.
  • Repository workspace path - The repository sub-folder ACE will use for saving workspace files. This setting enables you to keep multiple ACE workspaces in a single repository.
  • Runtime server port (Electron only) - The port used by the background server.

Once settings are supplied, click save. If save is successful, ACE is ready for development.

Troubleshooting​

Default branch does not exist​

Create the initial branch in git directly and try save the settings again

Invalid URL​

Try a different format of the same URL:

- https://identification@dev.azure.com/repositoryPath
+ https://dev.azure.com/repositoryPath

Private key not working​

Use access token (PAT) instead of private key

CORS​

legacy

Designer proxy service is removed starting with ACE version 5.28.0 and CORS behavior is handled implicitly.

Depending on the git provider, ACE proxy service and provider has to be configured to allow connection. Read more here.