cli: Change rad init default to not announce
As part of the continued effort of safe by default, rad init has been
updated to --no-announce, --announce has been introduced to enable
the prior behaviour. Additionally a message is supplied to the user
about their repository not being announced.
Some checks failed
— 0 passed, 1 failed
View logs ↗
14 files changed
+104
-18
b04f487b
→
94f6f11f
added crates/radicle-cli/examples/rad-init-no-announce.md
@@ -0,0 +1,47 @@
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
modified crates/radicle-cli/examples/rad-init-no-seed.md
@@ -1,6 +1,7 @@
|
|
| + | |
|
|
| - | |
| + | |
|
|
|
|
|
@@ -13,16 +14,19 @@ Your repository will be announced to the network when you start your node.
|
|
|
|
|
|
| + | |
|
|
|
|
|
|
|
|
|
|
| + | |
|
|
|
|
|
|
|
|
|
|
| + | |
|
|
|
|
|
modified crates/radicle-cli/examples/rad-init-private-no-seed.md
@@ -3,7 +3,7 @@ to be seeded. This means that the repo will be available locally, to us,
|
|
|
|
|
|
| - | |
| + | |
|
|
|
|
|
modified crates/radicle-cli/examples/rad-init-private.md
@@ -1,7 +1,7 @@
|
|
|
|
|
|
| - | |
| + | |
|
|
|
|
|
modified crates/radicle-cli/examples/rad-init-sync-not-connected.md
@@ -1,7 +1,7 @@
|
|
|
|
|
|
| - | |
| + | |
|
|
|
|
|
modified crates/radicle-cli/examples/rad-init-sync-preferred.md
@@ -1,7 +1,7 @@
|
|
|
|
|
|
| - | |
| + | |
|
|
|
|
|
modified crates/radicle-cli/examples/rad-init-sync-timeout.md
@@ -2,7 +2,7 @@ Sometimes, `init` will fail to sync with the network. This is not a big deal,
|
|
|
|
|
|
| - | |
| + | |
|
|
|
|
|
modified crates/radicle-cli/examples/rad-init-sync.md
@@ -3,7 +3,7 @@ To create your first radicle repository, navigate to a git repository, and run
|
|
|
|
|
|
| - | |
| + | |
|
|
|
|
|
modified crates/radicle-cli/examples/rad-init-with-existing-remote.md
@@ -20,7 +20,7 @@ $ git branch -vv
|
|
|
|
|
|
| - | |
| + | |
|
|
|
|
|
@@ -36,7 +36,7 @@ To push changes, run `git push rad master`.
|
|
|
|
|
|
| - | |
| + | |
|
|
|
|
|
modified crates/radicle-cli/examples/rad-init.md
@@ -3,7 +3,7 @@ To create your first radicle repository, navigate to a git repository, and run t
|
|
|
|
|
|
| - | |
| + | |
|
|
|
|
|
modified crates/radicle-cli/examples/rad-patch-pull-update.md
@@ -3,7 +3,7 @@ Let's look at how patch updates work.
|
|
|
|
|
|
| - | |
| + | |
|
|
|
|
|
modified crates/radicle-cli/src/commands/init.rs
@@ -59,6 +59,7 @@ pub fn init(repo: git::Repository, args: Args, profile: &profile::Profile) -> an
|
|
|
|
|
|
| + | |
|
|
|
|
|
@@ -133,6 +134,15 @@ pub fn init(repo: git::Repository, args: Args, profile: &profile::Profile) -> an
|
|
|
|
|
|
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
|
|
|
|
|
@@ -143,7 +153,7 @@ pub fn init(repo: git::Repository, args: Args, profile: &profile::Profile) -> an
|
|
|
|
|
|
| - | |
| + | |
|
|
|
|
|
@@ -204,12 +214,17 @@ pub fn init(repo: git::Repository, args: Args, profile: &profile::Profile) -> an
|
|
|
|
|
|
| - | |
| - | |
| - | |
| - | |
| - | |
| - | |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
|
|
|
|
|
modified crates/radicle-cli/src/commands/init/args.rs
@@ -55,6 +55,12 @@ pub struct Args {
|
|
|
|
|
|
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
|
|
|
|
|
@@ -83,6 +89,15 @@ impl Args {
|
|
|
|
|
|
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
| + | |
|
|
|
|
|
modified crates/radicle-cli/tests/commands.rs
@@ -228,6 +228,11 @@ fn rad_init() {
|
|
|
|
|
|
| + | |
| + | |
| + | |
| + | |
| + | |
|
|
|
|
|