Repository connections
Connect your organisation's GitHub, GitLab or Bitbucket account so its sites can deploy from Git, and disconnect one that is no longer used.
On this page
Before you start
- You are an owner, or your role has Manage Company Deployment Sources. Only an owner can disconnect an account.
- An agency connects an account for a client on the client's organisation page.
- The account belongs to the organisation, not to one person.
Connect GitHub, GitLab or Bitbucket
Open Deployments
Go to Organisation › Organisations, choose the organisation, then Deployments under Developers.
Sign in to the provider
Under Repository connections, choose Connect beside GitHub, GitLab or Bitbucket. Sign in there and approve access.
The account is listed under its provider as Connected. A provider can hold several accounts: choose Connect again to add another.
Connect your own GitLab server
Enter the server and a token
Choose Connect beside Self-hosted GitLab. Enter the Server address, starting
https://, and a Personal access token with theapiscope, then choose Connect.
The token is stored encrypted and never shown again.
Reconnect an account
Sign in again
Choose Reconnect on an account marked Needs re-authorising, and sign in to the provider again. For your own GitLab server, enter a new token.
Disconnect an account
Move the environments that use it
In each site's Deployments section, choose another connection for every environment that deploys through the account. An account still in use cannot be disconnected.
Disconnect
Choose Disconnect… on the account's row, then Disconnect.
Environments keep their deployed code.
Automate this
Answers the git provider accounts your own company deploys from, oldest first, 50 a page.
curl https://manage.corefinity.com/api/company/deployment-connections \
-H "Authorization: Bearer $COREFINITY_TOKEN" \
-H "Accept: application/json"Your assistant calls corestack_company_deployment_connections_list.
{
"name": "corestack_company_deployment_connections_list",
"arguments": {}
}