reviewos/reviewos.org
publicClone
Push over the same URL. A password will not work: create a token under access tokens and use it in place of one.
- .github
- app
- cli
- cloud
- config
- content
- database
- docs
- locales
- logs
- profile
- public
- resources
- routes
- scripts
- storage
- tests
- .dockerignore 161 B
- .editorconfig 147 B
- .env.example 29.2 KB
- .env.production 2.8 KB
- .gitattributes 12 B
- .gitignore 7.2 KB
- AGENTS.md 27.1 KB
- bootstrap 3.9 KB
- buddy 6.6 KB
- buddy-bot.config.ts 6.1 KB
- bun.lock 111.0 KB
- bunfig.toml 2.2 KB
- CHANGELOG.md 19.8 KB
- compose.yaml 7.1 KB
- deps.yaml 673 B
- Dockerfile 3.9 KB
- LICENSE.md 1.1 KB
- mirrors.yml 1.6 KB
- other.db 4.0 KB
- other.db-shm 32.0 KB
- other.db-wal 0 B
- package.json 4.1 KB
- pantry.lock 19.6 KB
- README.md 2.0 KB
- reviewos 24.0 KB
- reviewos-shm 32.0 KB
- reviewos-wal 253.5 KB
- rt2.tmp.ts 1.5 KB
- SECURITY.md 3.6 KB
- tsconfig.json 1.4 KB
ReviewOS
An open source, self-hostable git forge built around code review.
Most forges treat review as a tab on a pull request. ReviewOS treats it as the primary object: the repository browser, the diff viewer, and the notification system all exist to make reviewing code better. Stacked pull requests, review threads that survive a force-push, and a diff that stays fast at a hundred files are the point, not the extras.
ReviewOS is early. The roadmap in docs/todo is the honest picture of what exists and what does not.
What it will do
- Host git repositories over HTTPS, for users and organizations
- Issues, labels, and milestones
- Pull requests with first class reviews: approvals, requested changes, and threads anchored to a file, line, and side of the diff
- Webhooks, notifications, and a searchable explore page
- Run on your own hardware, with your data in your own Postgres
Requirements
- Bun 1.3.14 or newer
- PostgreSQL 17
- git 2.47 or newer
Pantry installs and manages all three. You do not need them on your machine beforehand.
Getting started
git clone https://github.com/ReviewOS/reviewos.org.git
cd reviewos.org
./buddy setup./buddy setup installs the toolchain, starts PostgreSQL, creates the database named in your
.env, and runs the migrations. Then:
./buddy devDevelopment
./buddy lint # pickier
./buddy typecheck # app/, config/, resources/, routes/
./buddy test # test suite
./buddy dev:docs # documentation site, including the roadmapData lives in models under app/Models/; migrations are generated from them with
./buddy generate:migrations and are never written by hand. AGENTS.md documents the conventions
in full, for humans as much as for coding agents.
Contributing
The roadmap in docs/todo is organized by phase, and every item is small enough to pick up on its own. Tick the box in the same commit as the work.