Collaborate & sync
Cloning, syncing, locking, and getting work reviewed. All transfer is TLS 1.3.
- Clone a repositorytovio clone, against a relay or a Forge.
- Clone only part of a repositorySparse, blobless, size-limited, shallow, and attachment-free clones.
- Push and pull in one steptovio sync, why divergence merges, and the one case that is still refused.
- Keep a repository synced continuouslysync --watch, and what auto-integration will not do.
- Fill in a partial clone latertovio fetch --deepen and --complete.
- Name your remotestovio remote add, list, show, remove — and what a name is actually used for.
- Serve a repository from your own machinetovio serve, for peer-to-peer work without a Forge.
- Pin a certificate for a native remote--cert, why it is required, and what a mismatch means.
- Lock a binary file so nobody else edits ittovio lock, for content that cannot be merged.
- Break a stuck lockReleasing a lock whose holder is gone.
- Propose a change for reviewtovio change propose, against a Forge.
- Review, approve or request changestovio review, and what a reviewer can see.
- Protect a laneRequiring review, checks, and reviewer coverage — and where to configure them.
- Land across several repositories atomicallyMeta-changes, for work that spans repositories.
- Signing in to the feedback portalThe available methods, why sign-in is required, and what a portal account is not.
- Tune automatic background syncAuto-sync is on by default. What triggers it, what it will not do, and how to change it.
- When a sync is refusedReading TVO-SYNC and connection errors, and what to do about each.
- Read a Forge's collaboration statetovio forge — proposals, checks, locks, webhooks, roster, and served policy.
- Stack a proposal on top of anotherchange propose --onto, for work that depends on a review still in flight.
- Decide which paths can be lockedLockable declarations, and why locking text is a mistake.