Documentation Index
Fetch the complete documentation index at: https://forge.laravel.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
Introduction
Source control providers allow Laravel Forge to access your project’s codebase and easily deploy your applications. Forge supports most popular Git providers as well as custom / self-hosted options. Source control providers are configured and managed within the organization’s settings.Supported providers
Laravel Forge supports the following source control providers:Managing source control providers
Connecting to a source control provider
To connect a source control provider, navigate to the organization’s settings. Then, on the “Source control” page, click “Add provider”. Select the provider you wish to connect to and authenticate your chosen account. You may only configure one account from each provider at a time. If you need to connect a different account from the same provider, you must first remove the existing connection.Removing source control providers
To unlink a source control provider, navigate to the organization’s settings. Then, on the “Source control” page, click the dropdown menu on the provider and click “Delete”.Refreshing tokens
To refresh a source control provider token, navigate to the organization’s settings. Then, on the “Source control” page, click the dropdown menu on the provider and click “Refresh token”.Updating source control access and permissions
To update your source control provider connection for accessing different organizations, repositories, or modifying token permissions:- Navigate to your source control provider’s settings
- Locate and uninstall the Laravel Forge application
- Return to Laravel Forge
- Click the Refresh Token button to initiate a new OAuth authentication flow
Using custom Git providers
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 theCustom 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).