Found in the 1.1.1 review. A batch of small command-line defects, each with a regression test.
gclo sync --dry-run that is canceled while the repositories are being listed exits 0 with an empty result, as if the organization had none.
gclo accounts add|edit|remove: a failure of the accounts file or of Windows Credential Manager ends with exit code 70 ("unexpected error, please report it"), where the help promises 2.
gclo accounts -h is reported as an unknown subcommand.
gclo accounts edit accepts a blank --rename, --org, or --target.
A relative --target is stored as typed, so the account means a different folder depending on where it is later used from (the desktop app, another working directory).
--description= is rejected although --description "" works.
The activity log of the CLI ignores GCLO_DATA_DIR: it always goes to the default data folder, while accounts and settings follow the variable.
Ctrl+C: commands that do not observe cancellation (accounts) and the interactive token prompt swallow the first Ctrl+C ("Canceling...") and then carry on.
Found in the 1.1.1 review. A batch of small command-line defects, each with a regression test.
- `gclo sync --dry-run` that is canceled while the repositories are being listed exits 0 with an empty result, as if the organization had none.
- `gclo accounts add|edit|remove`: a failure of the accounts file or of Windows Credential Manager ends with exit code 70 ("unexpected error, please report it"), where the help promises 2.
- `gclo accounts -h` is reported as an unknown subcommand.
- `gclo accounts edit` accepts a blank `--rename`, `--org`, or `--target`.
- A relative `--target` is stored as typed, so the account means a different folder depending on where it is later used from (the desktop app, another working directory).
- `--description=` is rejected although `--description ""` works.
- The activity log of the CLI ignores `GCLO_DATA_DIR`: it always goes to the default data folder, while accounts and settings follow the variable.
- Ctrl+C: commands that do not observe cancellation (`accounts`) and the interactive token prompt swallow the first Ctrl+C ("Canceling...") and then carry on.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Found in the 1.1.1 review. A batch of small command-line defects, each with a regression test.
gclo sync --dry-runthat is canceled while the repositories are being listed exits 0 with an empty result, as if the organization had none.gclo accounts add|edit|remove: a failure of the accounts file or of Windows Credential Manager ends with exit code 70 ("unexpected error, please report it"), where the help promises 2.gclo accounts -his reported as an unknown subcommand.gclo accounts editaccepts a blank--rename,--org, or--target.--targetis stored as typed, so the account means a different folder depending on where it is later used from (the desktop app, another working directory).--description=is rejected although--description ""works.GCLO_DATA_DIR: it always goes to the default data folder, while accounts and settings follow the variable.accounts) and the interactive token prompt swallow the first Ctrl+C ("Canceling...") and then carry on.