neosource docs
A forge built on a novel distributed engine, designed for many concurrent writers. You push with Git or jj.
neosource is a forge and hosting stack built on a novel distributed storage
engine of our own — one designed from the start for many writers at once, rather
than for a single machine holding a lock.
You push with Git, or with jj. Ordinary clone, ordinary push, ordinary
remotes. Nothing about the engine underneath is something you have to learn, and
the engine is not tied to either client — more protocols can follow.
Start here
Section titled “Start here”Why neosourceWhat this forge does differently, and where each of those things stops.
Getting startedCreate an account, create a repository, push to it.
Install the CLI
neo on macOS, Linux or Windows — optional, but good for issues, PRs and local CI.The storage engineWhat the engine is, and why it changes what a hosted forge can do.
PlanningTwo tracks — team tickets and repository issues — plus cycles, and how a change links to the work it belongs to.
Code reviewStacked pull requests, and review threads that survive a force-push.
Project statusWhat 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 hereWhere workflows live, and what triggers them.
Writing a workflowThe schema the parser actually accepts.
The job environment
packages:, not images.Coming from GitHub ActionsWhat works, what works with caveats, what does not.