CI/CD
Not yet. At launch, Gitza is the forge itself, done properly, hosted here. Hosted CI is on the roadmap with no date.
When it arrives it will be card-verified with hard caps, which is what keeps crypto-miners from burning the service down for everyone else. Free, unmetered compute attached to a Git host is an invitation, and a service that sells reliability cannot accept it.
If pipelines are the thing that decides whether you can move, say so on the waitlist . It is how we prioritise.
In the meantime
Gitza is a standard Git host, so any CI service that can clone a repository over HTTPS can build from it today:
- Generate an access token for the CI service, with read access to the repository and nothing else.
- Give the service the HTTPS clone address and the token.
- Add a webhook in the repository’s Settings → Webhooks so a push triggers a build rather than a poll.
Where your builds run is then up to that service, which is worth knowing if the reason you chose Gitza was residency: a pipeline that clones your code to a runner on another continent has moved a copy of it there.