pijul channel rename arguments named after their purpose This makes it so that calling `pijul channel rename something` will be reflected as providing the "to" argument, not the "from" argument. The help output also shows the "from" argument being optional, rather than "to" being optional which did not match the way the rename worked.
Dependencies
- [2]
5OGOE4VWStore the current channel in the pristine - [3]
JA4POQALRefactor channel command's handling of repo and channel - [4]
ZBNKSYA6Fixing a bus error when starting a transaction on a full disk - [5]
SXEYMYF7Fixing the bad changes in history (unfortunately, by rebooting). - [6]
Q4SVMHAERemoving --channel from the changes command - [7]
GKSVBEUWRefactor Repository constructors to take Option<&Path> instead of Option<PathBuf> - [8]
A3RM526YIntegrating identity malleability - [9]
VQPAUKBQchannel switch as an alias to reset
Change contents
- replacement in pijul/src/commands/channel.rs at line 27
#[clap(name = "rename")]Rename { from: String, to: Option<String> },#[clap(name = "rename", allow_missing_positional = true)]Rename { from: Option<String>, to: String }, - replacement in pijul/src/commands/channel.rs at line 92
let (from, to) = if let Some(to) = to {let (from, to) = if let Some(from) = from { - replacement in pijul/src/commands/channel.rs at line 95
(current, from.as_str())(current, to.as_str())