gy 2.2.0

good,yes — the ledger of what work rests on before a requirement is confirmed
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17

//! The `remote` group's leaves (n-8d0e): the three operations that decide where
//! the record lives, under one name. `set` / `join` / `sync` do what the old
//! top-level `share` / `join` / `sync` did; main.rs wires them.
use clap::Subcommand;

#[derive(Subcommand)]
pub enum RemoteAction {
    /// Start sharing: check the remote, write gy.toml, upload the ledger.
    Set {
        #[arg(value_name = "URL")]
        url: String,
    },
    /// Join a shared project: check what you need, take the copy, say who you write as.
    Join,
    /// Sync this copy with the remote named in gy.toml.
    Sync,
}