mab122
/
radicle-lfs-transfer
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: single git push rad now pushes commit + notes together

This commit is contained in:
Maciek "mab122" Bator 2026-07-16 15:23:13 +02:00
parent fe270dca8f
commit dd2af7c3d4
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
README.md
View File

@ -27,10 +27,10 @@ crate deliberately has no dependency on Radicle's identity/crypto stack; it just
staged LFS-tracked file's oid/size and passes them all to a single `rad lfs precommit` call,
which adds each one to your local IPFS daemon, pins it, encrypts it first if the repo is
private, and records the resulting CID as a git note (batched into one call, rather than one
per file, so a private repo's passphrase is only prompted for once per commit). Note that
committing the note locally and pushing it are separate steps in Radicle — pushing your
commit (`git push rad <branch>`) does **not** also push the notes ref; that needs a separate
bare `git push rad` (see radicle-heartwood-lfs's `LFS-IPFS.md` for the full explanation).
per file, so a private repo's passphrase is only prompted for once per commit). `rad lfs init`
configures the `rad` remote so a single `git push rad` pushes your commit and its notes
mapping together (see radicle-heartwood-lfs's `LFS-IPFS.md` for the full explanation) — as
long as it's been (re-)run with a build that includes that fix.
- `rad-lfs-transfer` implements the other half: when `git lfs push`/`pull` runs, it's invoked
per-object over stdin/stdout JSON (the standard Git LFS custom-transfer-agent protocol) and:
- **upload**: shells out to `rad lfs store --oid <oid> --size <size> <path>`, which is