Multi-Forge & Ticket Synchronization
CCCP connects your Git workflow directly to upstream issue trackers, automatically synchronizing open issues into a local markdown document (.antigravity/tickets.md) for developers and autonomous AI coding agents.
1. Supported Remote Forges
| Forge Ecosystem | Supported Domains | Active Probing & Identification |
|---|---|---|
| Forgejo & Gitea | codeberg.org, self-hosted |
Probes /api/v1/version for self-hosted instances |
| GitHub | github.com, GitHub Enterprise |
Uses GitHub REST API v3, filtering out pull requests |
| GitLab | framagit.org, gitlab.com, custom |
Probes /api/v4/version and supports nested subgroups |
| SourceHut | git.sr.ht, *.sr.ht |
Extracts issues via SourceHut GraphQL tracker |
2. Synchronizing Tickets (`cccp tickets`)
# Synchronize tickets using automatic remote forge detection:
cccp tickets
# Force a specific forge driver:
cccp tickets --provider forgejo
# Specify custom owner and repository slug:
TICKETS_OWNER=myteam TICKETS_REPO=myproject cccp tickets