You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Having scalar repos right next to scalar remove makes me concerned about confusion between the commands. In the future, should we have scalar repos remove take on the functionality of scalar remove? or scalar repos remove --from-disk while scalar repos remove just de-registers? Just something to think about.
As part of the planned scalar repos remove [<dir>] option (which de-registers the repo from the service), also add the --from-disk option.
The text was updated successfully, but these errors were encountered:
This PR is probably too large and I'll need to split it into smaller parts. However, it has the full story of how to redo our command-line interface:
* Commands `clone`, `diagnose`, `config`, `cache-server` are untouched.
* The `repos` command is dropped in favor of `register`, `list`, and `unregister`. Resolves#286.
* Created the `pause` and `resume` commands. Starts #284.
* Replaced `remove` with `delete`. Resolves#274.
* Reorganized the `docs` folder. Instead of a command reference page for each command, commands are grouped by purpose and documented together. These sections are:
- **Getting Started:** `clone`, `register`, `unregister`, `delete`.
- **Advanced:** `run`, `pause`, `resume`.
- **Troubleshooting:** `upgrade`, `diagnose`, `config`, `cache-server`.
Not done yet, but can be done in a later PR:
* Update the `README.md` with new information and point to the docs.
* `scalar run all` to run all maintenance tasks on an enlistment. (See #287)
from John:
As part of the planned
scalar repos remove [<dir>]
option (which de-registers the repo from the service), also add the--from-disk
option.The text was updated successfully, but these errors were encountered: