`coder schedule start`, `stop`, and `extend` printed the updated schedule as a fixed table with no `-o` or `-c`, while `coder schedule show` has both. All four commands now share one formatter with the same row type, default columns, `-o table|json`, and `-c`, so the output of a change and of `show` is interchangeable. **Behavior change:** Adds `-o` and `-c` to the three commands. The default table output changes slightly: the WORKSPACE column no longer includes the favorite-star prefix, matching `schedule show`. Other columns are unchanged. <details> <summary>Decisions</summary> - Previously these commands rendered `WorkspaceListRow`, which prefixes the workspace name with a favorite icon. Using `scheduleListRow` for consistency with `schedule show` drops that prefix. </details> Closes [CLI-15](https://linear.app/codercom/issue/CLI-15) _This PR was generated by Coder Agents on behalf of @nickvigilante._
26 lines
784 B
Plaintext
26 lines
784 B
Plaintext
coder v0.0.0-devel
|
|
|
|
USAGE:
|
|
coder schedule extend [flags] <workspace-name> <duration from now>
|
|
|
|
Extend the stop time of a currently running workspace instance.
|
|
|
|
Aliases: override-stop
|
|
|
|
Extends the workspace deadline.
|
|
* The new stop time is calculated from *now*.
|
|
* The new stop time must be at least 30 minutes in the future.
|
|
* The workspace template may restrict the maximum workspace runtime.
|
|
|
|
$ coder schedule extend my-workspace 90m
|
|
|
|
OPTIONS:
|
|
-c, --column [workspace|starts at|starts next|stops after|stops next] (default: workspace,starts at,starts next,stops after,stops next)
|
|
Columns to display in table output.
|
|
|
|
-o, --output table|json (default: table)
|
|
Output format.
|
|
|
|
———
|
|
Run `coder --help` for a list of global options.
|