Upstream repo bots; upstream CI in a copy we do not release from. Claude-Session: https://claude.ai/code/session_01HuMDfgFssPUptYUzgZ6Cp8
Hanzo Forge
Hanzo's self-hosted Git forge — Git hosting, code review, issues, packages, and CI/CD (GitHub-Actions-compatible), IAM-native via hanzo.id OIDC. Runs at git.hanzo.ai.
MIT licensed. Upstream authorship and licensing are recorded in NOTICE and LICENSE. Identity is wired to Hanzo IAM rather than local accounts.
Build & deploy
One way, like every Hanzo repo: the root hanzo.yml declares the
image and tests; a ~7-line .hanzo/workflows/cicd.yml
imports hanzoai/ci, which builds and pushes
ghcr.io/hanzoai/git on our own runners against git.hanzo.ai. Never build the image locally.
The running service is defined in hanzoai/universe (the git operator App CR):
a single-writer SQLite deployment, config injected via the GIT__<section>__<KEY>
env contract, OIDC login reconciled to hanzo.id.
Development
See docs/development.md for a local environment.
After building, run ./gitd web to start the server, or ./gitd help for
all commands.