Skip to content
Colony Docs

Integrations

Colony works with the tools you already use. This page covers the categories and how to think about each. Setup steps live in the Self-Host or Cloud pillars.

Version control

Section titled “Version control”

Colony reads from and writes to your version control system. Today:

  • GitHub — first-class. Issues, comments, labels, PRs, branch protections, merge queues all integrate.
  • Azure DevOps — supported. Work items, pull requests, builds.

The VCS is the source of truth for issues and code; Colony’s Pipeline Store is the source of truth for pipeline state. Labels and tags are projections of pipeline state into the VCS — they’re a convenience for humans inspecting status, not a control surface.

CI

Section titled “CI”

Colony cooperates with your existing CI. Two patterns:

  • CI gates merges — your existing CI runs on Colony’s PRs as it does on human PRs. Failed checks block merge. This is the default and works without configuration.
  • CI signals Colony — Colony’s reviewer worker reads CI results to inform its review. Failed CI prompts the reviewer to request changes; passing CI is one input among many.

Colony does not replace your CI. It runs alongside.

Notifications

Section titled “Notifications”

Colony emits events as humans expect them:

  • PR review pings when a PR transitions to human-review-ready
  • Issue comments when the analyzer needs clarification
  • Escalation routing when the colony asks an Operator for help

How those events surface depends on your VCS configuration (GitHub notifications, Azure DevOps subscriptions) and the channels you wire up.

Identity and SSO

Section titled “Identity and SSO”

Authentication for the dashboard supports:

  • GitHub OAuth (Cloud, default)
  • SSO via SAML/OIDC (Cloud, available on Business and Enterprise plans)
  • Self-hosted identity — whatever your deployment is configured for

Where to go for setup

Section titled “Where to go for setup”