neosource docs
A forge built on a content-addressed storage engine — distributed repository operations without a single-node bottleneck.
neosource is a forge and hosting stack built on a content-addressed storage
engine: immutable objects, an append-only operation log, and compare-and-swap
operation heads.
Push with Git today. jj is first-class too — it works over the same endpoints, if you want it. The engine is protocol-agnostic by construction.
Start here
Section titled “Start here”- Getting started — create an account, create a repository, push to it.
- The storage engine — what the engine is, and why it changes what a hosted forge can do.
- Protocols: Git and jj — how the protocol edge relates to the engine underneath.
- Project status — what is ready today, and what is not.
neosource runs CI from workflows in .neosource/workflows/. The YAML is
deliberately close to GitHub Actions, with one large divergence: jobs declare the
tools they need with packages: instead of choosing a container image.
- How CI works here — where workflows live, and what triggers them.
- Writing a workflow — the schema the parser actually accepts.
- The job environment —
packages:, not images. - Coming from GitHub Actions — what works, what works with caveats, what does not.