Platforms
Every platform answers the same nine resources with the same shapes. What changes underneath is the API, the header the token travels in, how a page says there is a next one, and which operations exist at all. The pages are short on purpose. The part worth reading is the gotcha list on each one.
| Platform | Provider | Auth | Threads | Code search | Templates |
|---|---|---|---|---|---|
| GitHub | github | Authorization: token | GraphQL, real flags | global, owner, repository | repository and owner .github |
| GitLab | gitlab | Private-Token | REST discussions, token required | token required, Premium for global | effective templates, source may be hidden |
| Gitea | gitea | Authorization: token | one per review comment | none | repository only |
| GitBucket | github + baseURL | Authorization: token | none | none | repository only |
icon: i-simple-icons-github to: /platforms/github title: GitHub
REST v3 for everything except review threads, which need GraphQL for their resolved flag. The reference the others are measured against.
icon: i-simple-icons-gitlab to: /platforms/gitlab title: GitLab
API v4 with Private-Token auth, project ids resolved and cached for you, iid as the number, and a group fallback for owners that are not users.
icon: i-simple-icons-gitea to: /platforms/gitea title: Gitea and Forgejo
API v1 with limit instead of per_page, empty strings and nulls where fields are missing, and Codeberg or any Forgejo through baseURL.
icon: i-lucide-server to: /platforms/gitbucket title: GitBucket
The GitHub provider pointed at a GitBucket /api/v3. What GitBucket does not serve fails with a sentence, not a 404.