Connections
About Connections
The Connections page links your GitHub and GitLab accounts to ACTIVATE, enabling repository access on the platform. Remote workflows, the uses field, pw workflows run, and the checkout action read repositories as you, so they can only reach projects your linked account can see.
Note
The GitHub connection is available once a platform administrator has configured the platform's GitHub integration. GitLab servers are registered per organization by an organization administrator; the GitLab card only appears once your organization has registered at least one server. If an option isn't available, contact your administrator.
Navigate to your account settings (Username > Account). On the next page, click Connections.
The page shows one card per provider.
GitHub
Link Your GitHub Account
On the GitHub card, click Link GitHub. A GitHub authorization window will open; follow the prompts to authorize the connection.
Once linked, the card shows Connected as @username, and a dialog box with the message GitHub account linked successfully will appear.
Install the GitHub App
After linking your account, install the GitHub App wherever you want to grant repository access:
- The Connected organizations section lists the GitHub organizations where the app is installed, along with each installation date. Click the plus icon to install the app on another organization.
- The Personal GitHub account section shows whether the app is installed on your personal account.
To manage an existing installation's repository access, open its Connected dropdown menu and click Configure in GitHub.
Disconnect Your GitHub Account
On the GitHub card, click the delete icon. A dialog box will appear with the message Are you sure you want to disconnect your GitHub account? You will need to re-link to access repositories.
Click Disconnect. A dialog box with the message GitHub account disconnected will appear.
GitLab
The GitLab card lists every GitLab server your organization has registered. Each server is connected separately, and the buttons on a row show how that server lets you connect: Connect (OAuth), Use a token (personal access token), or both.
Connect with OAuth
On the server's row, click Connect.
A GitLab authorization window will open. Sign in to GitLab if prompted and click Authorize. ACTIVATE only requests the read_api scope.
Once connected, the row shows Connected as username on hostname, and a dialog box with the message GitLab account connected will appear.
Connect with a Personal Access Token
On the GitLab server, create a personal access token with the read_api scope (User settings > Access tokens).
On the server's row, click Use a token.
Paste the token into the dialog box and click Use a token.
The token is verified against the server before it is stored. Once connected, the row shows Connected as username on hostname with a personal access token.
Note
ACTIVATE stores the token in the platform vault and forgets it when you disconnect, but never revokes it. Revoke the token in GitLab yourself when you no longer need it.
Disconnect a GitLab Server
On the server's row, click the delete icon.
A dialog box will appear with the message Disconnect your account on server? Workflows will no longer be able to read your repositories there. Click Disconnect.
A dialog box with the message GitLab account disconnected will appear. You can reconnect at any time.