Skip to content

Repos & Access (VCS Connections)

The Repos & Access settings page (Settings → Repos & access) manages the GitHub App connections that Colony uses to interact with your code and the list of repositories Colony is authorized to process.

Colony Cloud uses two GitHub Apps. Each connects independently and covers a distinct set of permissions.

AppTypePermissions
colony-coderRequiredCreate branches, push code, open and merge pull requests
colony-operationsOptionalPost review comments, manage issue labels, update issue status

Without colony-coder, Colony cannot perform any code operations. Without colony-operations, Colony still creates PRs and pushes code but cannot post review comments or manage issues under its own identity.

  1. Open Settings → Repos & access.
  2. On the colony-coder card, click Install colony-coder. Colony Cloud redirects you to GitHub’s App installation page.
  3. On GitHub, select the organization or account to install the app on, then choose which repositories to grant it access to.
  4. Click Install & Authorize. GitHub redirects you back to Colony Cloud, which records the connection automatically.

After the redirect completes, the colony-coder card shows Connected and the Repositories list appears below.

colony-operations can only be installed after colony-coder is connected.

  1. On the colony-operations card, click Install colony-operations.
  2. Complete the GitHub App installation flow as with colony-coder.
  3. GitHub redirects back; Colony Cloud records the connection.

If your Colony Cloud organization spans multiple GitHub organizations, you can connect colony-coder to additional GitHub orgs from the same page.

  1. Ensure at least one colony-coder connection is active.
  2. Click + Connect another GitHub org below the connection cards.
  3. Complete the GitHub installation flow for the additional GitHub organization.

Each connected GitHub org appears as a labeled group in the connections list. The repository list aggregates repos from all connected orgs.

  1. On the card for the app you want to disconnect, click Disconnect.
  2. Confirm the dialog.

colony-coder disconnect: The confirm dialog requires you to type the GitHub organization name before the button becomes active. Disconnecting colony-coder immediately halts all pipeline processing for that org — Workers can no longer create branches or push code until the app is reconnected.

colony-operations disconnect: No name confirmation required. Disconnecting disables automated review comments and issue label management; code generation via colony-coder continues unaffected.

The Refresh connection status button verifies that stored app connections are still active by attempting to generate an installation token for each one.

  • Connections that are confirmed gone (GitHub returns a definitive removal response) are removed from Colony Cloud.
  • Connections where verification fails transiently (GitHub outage, network error) are preserved — Colony does not remove them on uncertainty.
  • Connections that are successfully verified remain unchanged.

Refresh does not discover new installations. New connections are recorded only via the GitHub App install flow described above.

The Repositories section lists every repository that colony-coder has been granted access to across all connected GitHub orgs. Use the toggle next to each repository to control whether Colony processes issues in it.

Toggle stateBehavior
EnabledColony monitors and processes new issues for this repository
DisabledColony ignores new issues; existing pipeline runs are not interrupted

Toggling a repository on or off takes effect immediately.

The list only shows repositories that the colony-coder GitHub App has been explicitly granted access to. If a repository you want to enable is not listed:

  1. Go to your GitHub organization settings.
  2. Navigate to Installed GitHub Apps → colony-coder → Configure.
  3. Under Repository access, add the repository.
  4. Return to Colony Cloud — the repository appears in the list immediately.
  1. Locate the repository in the list.
  2. Click its toggle to turn it off.
  3. Confirm the dialog. Colony stops picking up new issues for this repository immediately.

Disabling a repository does not delete any history or configuration. Re-enable it at any time by toggling it back on.

ActionRequired role
Install colony-coder or colony-operationsOwner or Admin
Connect another GitHub orgOwner or Admin
Disconnect an appOwner or Admin
Refresh connection statusOwner or Admin
Enable or disable a repositoryOwner or Admin
View the repository listAny member
MethodPathRequired roleDescription
GET/api/orgs/:orgId/installationsOwner, AdminList all GitHub App installations for the org
POST/api/orgs/:orgId/installations/refreshOwner, AdminVerify stored connections and remove confirmed-gone ones
POST/api/orgs/:orgId/installations/:appType/connectOwner, AdminInitiate a GitHub App installation (returns install URL)
DELETE/api/orgs/:orgId/installations/:appTypeOwner, AdminDisconnect a GitHub App installation
GET/api/orgs/:orgId/reposAny memberList repositories accessible to colony-coder
PUT/api/orgs/:orgId/repos/:externalRepoIdOwner, AdminEnable or disable a repository

:appType is coder or operations. On DELETE, pass ?externalOrgId=<id> to scope the disconnect to a specific GitHub org in a multi-tenant setup.