onevcs
Version control and its remote host behind one host-neutral vocabulary, for agent workflows.
The review unit is a change request — GitHub maps it to a pull request, and a
later host maps it to whatever it calls the same thing. Vcs owns the repository
side (identities, sessions over an isolated worktree, preserved work);
RemoteHost owns the host side (opening a change, reading its checks, merging
it); a rules file decides, per repository, how a change publishes and what
verifies it. Everything a run does is emitted as an NDJSON event stream.
The public surface is the approved contract — docs/contract.md
— compiled, and it is implemented: the registry with its lazy migration, the rules
engine, sessions over borrowing clones, bounded git, the FIFO merge queue, both
publication strategies, recovery and provenance, the merge train, and the event
stream.
What one change looks like
onevcs register ~/projects/widgets # once per checkout
onevcs rules check widgets # which policy, and why
token=$(onevcs session open widgets --branch feature/thing | jq -r .token)
# …work in the worktree the session printed…
onevcs publish "$token" # verify, then land it
onevcs events "$token" # everything it did, as NDJSON
Everything durable lives under one state root — ONEVCS_HOME, otherwise
~/.onevcs.
GitHub is reached through gh, so whatever gh auth status reports is the
credential. A fine-grained personal access token needs Actions: Read on the
repository beside its contents and pull-requests access: GitHub will not let that
credential class resolve a check run at all — there is no Checks permission to
grant one — so a change request's checks are read from its workflow runs, and
change_checks says so in the sources it answers with. Anything a third-party
integration posted as a check run or a commit status is invisible to such a token,
and a credential that can read neither source is refused rather than reported as
having no checks.
Install
cargo install onevcs # crates.io
pip install onevcs-cli # a prebuilt wheel, no Rust toolchain
npm install -g onevcs-cli # a prebuilt binary, no Rust toolchain
All three install the same onevcs binary. Prebuilt binaries exist for Linux
(x64, arm64), macOS (x64, arm64), and Windows (x64); every release also attaches
the archives and their .sha256 checksums for a direct download.
Use
onevcs --help
--help is the command surface, and publish reserves its own exit codes for a
gate that failed, a request that was invalid, and a base that moved under it.
Embed it
A command answers a process: an exit code and a line of prose. A caller embedding the crate wants the decision, so the same operations answer values.
let published = onevcs::publish(&providers, &token, &PublishRequest::default())?;
match published.outcome {
PublishOutcome::Merged(sha) => journal.landed(sha),
PublishOutcome::ChangeOpen(url) | PublishOutcome::Queued(url) => journal.awaiting(url),
PublishOutcome::NothingToPublish => journal.nothing(),
PublishOutcome::Failed { kind, reason, retained } => journal.failed(kind, reason, retained),
}
close_session and session are the same for the rest of a session's life, and
EventStream::open(&token) reads its events as Envelopes, each attributed to
the session that wrote it — so a caller following several publications at once can
tell them apart. The command line is a rendering of these rather than a second
path through them.
Test against it, without a real GitHub
Embedding the crate, run_with(&cli, providers) takes the two implementations a
run reaches Vcs and RemoteHost through; run is that with Git and GitHub,
and every entry point above goes through the same seam.
onevcs-testing ships in-memory and file-backed
implementations of both, so a consumer's suite drives a real onevcs through a
real journey against a host it seeded:
cargo add --dev onevcs-testing
They emit the events the real implementations emit — a claim this repository's own suite checks by running one publication journey on both backends and holding the two event streams to each other.
Develop
just bootstrap # from a clean clone
just check # the deterministic gate: format, clippy, tests, coverage, docs
just gate # check, plus the diff-scoped LLM-judge tier — the pre-push bar
just --list is the full index.
License
MIT. See LICENSE.
1 maintainer
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distributions
Built Distributions
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file onevcs_cli-0.2.5-py3-none-win_amd64.whl.
File metadata
- Download URL: onevcs_cli-0.2.5-py3-none-win_amd64.whl
- Upload date:
- Size: 1.0 MB
- Tags: Python 3, Windows x86-64
- Uploaded using Trusted Publishing? No
- Uploaded via:
twine/7.0.0 CPython/3.13.14
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
030faf47f6070dbe9663386c33814de183e7bdf384a21a430c84aca9dcbce66a
|
|
| MD5 |
4b028a571e3f92666dd03bfde434b81a
|
|
| BLAKE2b-256 |
a98f506502fc43fec2ae5072f63b0696ac3e71b3dc53ff31a74d0bc25b9abd2e
|
File details
Details for the file onevcs_cli-0.2.5-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.
File metadata
- Download URL: onevcs_cli-0.2.5-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
- Upload date:
- Size: 1.0 MB
- Tags: Python 3, manylinux: glibc 2.17+ x86-64
- Uploaded using Trusted Publishing? No
- Uploaded via:
twine/7.0.0 CPython/3.13.14
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
fde36f758f9754775dd416739a44ade5ca9bad77bbf8ababa232135f63ee9a1e
|
|
| MD5 |
44f8b92c13bbc577c53c51d8f6a964dd
|
|
| BLAKE2b-256 |
7fee51e573b12911c2b84bb00caaabab7badce021b1a5fe5f78d185ffa7e3a95
|
File details
Details for the file onevcs_cli-0.2.5-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.whl.
File metadata
- Download URL: onevcs_cli-0.2.5-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
- Upload date:
- Size: 963.5 kB
- Tags: Python 3, manylinux: glibc 2.17+ ARM64
- Uploaded using Trusted Publishing? No
- Uploaded via:
twine/7.0.0 CPython/3.13.14
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
f3fe58c08f0afd7acc9404402a3923a45856649b205163b4e5bcb96777aa0e8e
|
|
| MD5 |
3419ef606696889fe9c4fa91b43f3795
|
|
| BLAKE2b-256 |
e93cfcce0892499162ef777fd7bf5a9072897acc04b2d5f3837a4a50bb3187cc
|
File details
Details for the file onevcs_cli-0.2.5-py3-none-macosx_11_0_arm64.whl.
File metadata
- Download URL: onevcs_cli-0.2.5-py3-none-macosx_11_0_arm64.whl
- Upload date:
- Size: 949.8 kB
- Tags: Python 3, macOS 11.0+ ARM64
- Uploaded using Trusted Publishing? No
- Uploaded via:
twine/7.0.0 CPython/3.13.14
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
bf15c390e5195eb645901a9e994b791231332b7bba0c3ca415025c89a43ee171
|
|
| MD5 |
a98821b917b37c28a09cbef8ee7c56b5
|
|
| BLAKE2b-256 |
21dd13926a3401b54680a34b7642ec4b215d956dc05e207b5ff6efc84523d03e
|
File details
Details for the file onevcs_cli-0.2.5-py3-none-macosx_10_12_x86_64.whl.
File metadata
- Download URL: onevcs_cli-0.2.5-py3-none-macosx_10_12_x86_64.whl
- Upload date:
- Size: 1.0 MB
- Tags: Python 3, macOS 10.12+ x86-64
- Uploaded using Trusted Publishing? No
- Uploaded via:
twine/7.0.0 CPython/3.13.14
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
2833a51884f08e52fb74118cafe644ed2c9685b6ee06291ace9c7eaa2b692db1
|
|
| MD5 |
01bbf7a3a0010dfb90457354ff5c3e19
|
|
| BLAKE2b-256 |
f7413d551f8623f24931f64eb70c66273b18ec5fb7fc9004ba5ba9988a996c8f
|
