From 345ca923801aa13f124526c2e6431acc5823a0a8 Mon Sep 17 00:00:00 2001 From: cloudhead Date: Tue, 11 Jun 2024 14:09:44 +0200 Subject: [PATCH] cli: Clarify doc test example --- radicle-cli/examples/rad-init-private-no-seed.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/radicle-cli/examples/rad-init-private-no-seed.md b/radicle-cli/examples/rad-init-private-no-seed.md index 575ad8ef..9b3bd246 100644 --- a/radicle-cli/examples/rad-init-private-no-seed.md +++ b/radicle-cli/examples/rad-init-private-no-seed.md @@ -1,5 +1,7 @@ Let's say we initialize a private repository and specify that we don't want it -to be seeded. +to be seeded. This means that the repo will be available locally, to us, +and even if other peers know about it, they won't be able to fetch it +from us. ``` $ rad init --name heartwood --description "radicle heartwood protocol & stack" --no-confirm --private --no-seed @@ -22,7 +24,8 @@ $ rad seed No seeding policies to show. ``` -We can decide to seed it later: +We can decide to seed it later, so that others can fetch it from us, given +that they are part of the allow list: ``` $ rad seed rad:z2ug5mwNKZB8KGpBDRTrWHAMbvHCu ✓ Seeding policy updated for rad:z2ug5mwNKZB8KGpBDRTrWHAMbvHCu with scope 'all'