modified radicle-cli/examples/rad-fetch.md
@@ -9,13 +9,13 @@ storage. In this scenario, we know that the project is
|
|
|
|
|
|
| - | |
| + | |
|
|
| - | |
|
|
|
|
|
|
| - | |
| + | |
| + | |
|
|
|
|
|
modified radicle-cli/examples/rad-node.md
@@ -35,7 +35,7 @@ those commands we'll first track a peer so that we have something to
|
|
|
|
|
|
| - | |
| + | |
|
|
|
|
|
modified radicle-cli/examples/rad-track.md
@@ -2,7 +2,7 @@ To configure our node's tracking policy, we can use the `rad track` command.
|
|
|
|
|
|
| - | |
| + | |
|
|
|
|
|
modified radicle-cli/examples/workflow/5-patching-maintainer.md
@@ -5,7 +5,6 @@ Changes have been proposed by another person (or peer) via a radicle patch. To
|
|
|
|
|
|
| - | |
|
|
|
|
|
@@ -15,7 +14,8 @@ Additionally, we need to add a new 'git remote' to our working copy for the
|
|
|
|
|
|
| - | |
| + | |
| + | |
|
|
|
|
|
modified radicle-cli/src/commands/track.rs
@@ -6,6 +6,7 @@ use radicle::node::tracking::{Alias, Scope};
|
|
|
|
|
|
| + | |
|
|
|
|
|
@@ -16,7 +17,7 @@ pub const HELP: Help = Help {
|
|
|
|
|
|
| - | |
| + | |
|
|
|
|
|
@@ -30,7 +31,7 @@ Usage
|
|
|
|
|
|
| - | |
| + | |
|
|
|
|
|
@@ -94,7 +95,8 @@ impl Args for Options {
|
|
|
|
|
|
| - | |
| + | |
| + | |
|
|
|
|
|
@@ -121,15 +123,17 @@ pub fn run(options: Options, ctx: impl term::Context) -> anyhow::Result<()> {
|
|
|
|
|
|
| - | |
| - | |
| - | |
| + | |
| + | |
| + | |
| + | |
| + | |
|
|
| - | |
| - | |
| - | |
| + | |
| + | |
| + | |
| + | |
|
|
| - | |
|
|
|
|
|