Thanks to visit codestin.com
Credit goes to github.com

Skip to content

docs: note bulk stop confirmation #27908

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jakehwll merged 1 commit into from
Aug 6, 2026
Merged

docs: note bulk stop confirmation #27908

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/user-guides/workspace-management.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@
environments that are identically configured and provisioned with the same
resources.

## Creating workspaces

Check warning on line 12 in docs/user-guides/workspace-management.md

View workflow job for this annotation

GitHub Actions / lint-docs

Coder.GerundHeading 

Heading starts with an -ing word ('Creating'); prefer the imperative ('Install') or the noun ('Installation'). See capitalization-and-punctuation.md#no-gerund-leading-headings.

You can create a workspace in the UI. Log in to your Coder instance, go to the
**Templates** tab, find the template you need, and select **Create Workspace**.
Expand Down Expand Up @@ -70,7 +70,7 @@
- `id` - Workspace UUID
- `healthy` - Only applicable for workspaces in "start" transition. `healthy:false` is an alias for `has-agent:timeout,disconnected`, `healthy:true` is an alias for `has-agent:connected`.

## Updating workspaces

Check warning on line 73 in docs/user-guides/workspace-management.md

View workflow job for this annotation

GitHub Actions / lint-docs

Coder.GerundHeading 

Heading starts with an -ing word ('Updating'); prefer the imperative ('Install') or the noun ('Installation'). See capitalization-and-punctuation.md#no-gerund-leading-headings.

After updating the default version of the template that a workspace was created
from, you can update the workspace.
Expand All @@ -80,7 +80,7 @@
If the workspace is running, Coder stops it, updates it, then starts the
workspace again.

### Updating via the CLI

Check warning on line 83 in docs/user-guides/workspace-management.md

View workflow job for this annotation

GitHub Actions / lint-docs

Coder.GerundHeading 

Heading starts with an -ing word ('Updating'); prefer the imperative ('Install') or the noun ('Installation'). See capitalization-and-punctuation.md#no-gerund-leading-headings.

Update a workspace through the command line:

Expand Down Expand Up @@ -110,12 +110,12 @@
The start and stop operations can be applied even when the selected workspaces
are not all in the same state. Bulk start will only apply to selected workspaces
that are currently stopped, and bulk stop will only apply to selected workspaces
that are currently running. For update and delete, the user will be prompted for
confirmation before any action is taken.
that are currently running. For update, delete, and stop, the user is prompted
for confirmation before any action is taken.

![Bulk workspace actions](../images/user-guides/workspace-bulk-actions.png)

## Starting and stopping workspaces

Check warning on line 118 in docs/user-guides/workspace-management.md

View workflow job for this annotation

GitHub Actions / lint-docs

Coder.GerundHeading 

Heading starts with an -ing word ('Starting'); prefer the imperative ('Install') or the noun ('Installation'). See capitalization-and-punctuation.md#no-gerund-leading-headings.

By default, you manually start and stop workspaces as you need. You can also
schedule a workspace to start and stop automatically.
Expand All @@ -142,7 +142,7 @@
though the exact behavior depends on the template. For more information, see
[Resource Persistence](../admin/templates/extending-templates/resource-persistence.md).

## Repairing workspaces

Check warning on line 145 in docs/user-guides/workspace-management.md

View workflow job for this annotation

GitHub Actions / lint-docs

Coder.GerundHeading 

Heading starts with an -ing word ('Repairing'); prefer the imperative ('Install') or the noun ('Installation'). See capitalization-and-punctuation.md#no-gerund-leading-headings.

Use the following command to re-enter template input variables in an existing
workspace. This command is useful when a workspace fails to build because its
Expand Down
Loading