neosource docs

neosource is a code-hosting forge built on a fast content-addressed engine and a modern, responsive UI. It is built for people first — planning, code review, CI/CD, and packages live together in one product without enterprise feature-gating — with future AI plans designed around the same foundation.

It works with any Git client: git itself, jj through its Git support, and your IDE. Ordinary clone, ordinary push, ordinary remotes — nothing new to learn before you start pushing code.

Start here

Why neosource Human writtenWhy this forge exists, what it does differently, and where each of those things stops.

Getting startedCreate an account, create a repository, push to it.

Install the CLIneo on macOS, Linux or Windows — optional, but great for issues, PRs, and local-first CI.

PlanningTwo tracks — team tickets and repository issues — plus cycles, triage, and automatic PR linking.

Code reviewStacked pull requests, a speculative merge queue, and review threads that survive a force-push.

The storage engineHow the lock-free content-addressed engine underneath works.

Project statusWhat is ready today, what has sharp edges, and what is not built yet.

CI/CD

neosource runs CI from workflows in .neosource/workflows/ (or .github/workflows/ when enabled). The YAML follows GitHub Actions, runs each job in an isolated virtual machine with a persistent copy-on-write cache disk and real upstream actions, and lets jobs declare extra tools with packages: instead of maintaining container images.

How CI works hereWhere workflows live, what triggers them, and how concurrency and job ordering work.

Writing a workflowThe full workflow schema: triggers, filters, jobs, matrices, services, and diagnostics.

The job environmentPre-installed toolchains, declarative packages: or a flake: dev shell, and how to choose.

Coming from GitHub ActionsWhat works unchanged, what works with caveats, and what does not exist yet.