Connect a Repository
Connecting a repository tells Colony Cloud to manage that repository’s issues through the autonomous pipeline. You can connect multiple repositories under the same organization.
Enable a repository
Section titled “Enable a repository”- In Colony Cloud, open Account → Tenants → your tenant → Repositories (
/account/tenants/:tenantId/repositories). - In the Repositories list, find the repository you want to connect. If it is not listed, widen the colony-coder GitHub App’s repository access on GitHub. The list only shows repositories the app has been explicitly granted access to. See Adding repositories to the list.
- Turn on the repository’s toggle. Enabling takes effect immediately, with no confirmation.
Enabling a repository creates records in two places at once:
- A record in Colony Cloud linking the repository to your organization.
- Records in Colony’s Pipeline Store that register the repository with the autonomous pipeline and apply your organization’s default configuration.
Once the toggle is on, Colony picks up proposals you authorize and items you mark for Colony. It doesn’t pick up every new item unless you set Intake mode to All issues.
Configure repository settings
Section titled “Configure repository settings”Each repository has its own pipeline configuration. Open the repository’s settings to customize how Colony handles it.
- Pick the repository in the repository control in the hub header.
- Open Operations → Settings (
/operations/settings?repo=<owner>/<name>).
Conventions
Section titled “Conventions”The most important configuration for a repository is its .colony/conventions.md file — a Markdown document that describes the codebase’s tech stack, coding conventions, forbidden patterns, and review priorities. Colony’s agents read this file before analyzing, developing, or reviewing any issue in the repository.
Place .colony/conventions.md in the repository root and commit it to the default branch. Colony reads the file on every pipeline run — changes take effect immediately without reconfiguring the repository in Colony Cloud.
See Build and Maintain Repository Conventions for what belongs in the file and how to validate it.
Pipeline tracks
Section titled “Pipeline tracks”Self-improvement (SI) tracks let Colony propose work proactively — analyzing the repository on a schedule and filing issues for improvements such as test coverage, type tightening, or dependency updates — without waiting for a human to file an issue. Tracks are configured per repository on the Autonomy → Tracks page (/autonomy/tracks), scoped to the repository.
For full configuration and monitoring details, see Self-Improvement Tracks.
Worker capacity
Section titled “Worker capacity”Worker capacity is managed under Operations → Fleet (/operations/fleet). Organizations with multi-repository pool mode configure a tenant-wide pool size; other BYO deployments use the repository-scoped commands generated with a registration token. The repository settings page does not reserve a private Worker allocation for one repository.
See Workers and Operate and Scale Workers before changing capacity.
Disable a repository
Section titled “Disable a repository”Disabling a repository tells Colony to stop processing new issues. It does not delete any history or configuration.
- Open Account → Tenants → your tenant → Repositories (
/account/tenants/:tenantId/repositories). - In the Repositories list, turn off the repository’s toggle.
- In the Disable repository dialog, confirm. The dialog reads “Disabling
<owner/name>will immediately stop Colony from processing new issues for this repository.”
Disabling needs the org admin role. See Disabling a repository for the full flow.
When you disable a repository:
- Colony stops picking up new issues immediately.
- Issues currently being worked (in states such as
ready-for-devorin-review) are allowed to finish their current task. They are not aborted mid-run. - The repository is marked inactive. No Pipeline Store data is deleted.
- Re-enable it at any time by turning the toggle back on. Re-enabling needs no confirmation.