​
Introduction

Source providers allow Forge to access your project’s codebase to help you easily deploy your applications. Forge supports most popular Git providers as well as custom / self-hosted options.

​
Supported Providers

Forge currently supports the following source control providers:

​
Using A Custom Git Provider

If your Git Provider is not a first-party provider, then you may use the Custom option when creating a new site on your server.

First, choose the Custom option when creating your Git based site. Next, add the generated SSH key to your source control provider and provide the full repository path (git@provider.com:user/repository.git).

​
Provider Management

​
Connecting Providers

You can connect to any of the supported source control providers at any time through Forge’s Source Control dashboard within your Forge account profile.

​
Unlinking Providers

You may remove a connected source control provider by clicking the Unlink button next to a provider.

You won’t be able to unlink your provider if there are sites that depend on it.

​
Refreshing Tokens

If you would like to refresh Forge’s connection to your source control provider, you may do so by clicking the Refresh Token button next to the source control provider’s name on the Source Control dashboard within your Forge account profile.

​
Updating Source Control Access and Permissions

To update your source control provider connection for accessing different organizations, repositories, or modifying token permissions:

  1. Navigate to your source control provider’s settings
  2. Locate and uninstall the Forge OAuth application
  3. Return to Forge
  4. Click the Refresh Token button to initiate a new OAuth authentication flow

When you need access to different organizations or repositories, simply refreshing the token may not grant the necessary permissions. Following the complete OAuth authentication flow allows you to explicitly authorize access to your desired organizations and repositories with the appropriate permission scope.