Skip to content

docs(site): Mention template editor in template edit docs #7261

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.

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
merged 4 commits into from
Apr 26, 2023
Merged
Changes from 1 commit
Commits
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
Prev Previous commit
Next Next commit
Apply suggestions from code review
Co-authored-by: Kira Pilot <kira@coder.com>
  • Loading branch information
BrunoQuaresma and Kira-Pilot authored Apr 25, 2023
commit c5c13e1a2457d2b7f1103c0f2ce596435d1d5d09
4 changes: 2 additions & 2 deletions docs/templates/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -247,9 +247,9 @@ resource "kubernetes_pod" "podName" {
You can edit a template using the coder CLI or the UI. Only [template admins and
owners](../admin/users.md) can edit a template.

Using the UI, navigate to the template page, click on the "three dots" button, and select the option "Edit files". In the template editor, you create, edit and remove files. After every change, you have to build the template with the new modifications, to test if they are valid, and after you can publish them make the new template version the active one (the version that is used by default) or not.
Using the UI, navigate to the template page, click on the Kebab menu, and select the option to "Edit files". In the template editor, you create, edit and remove files. Before publishing a new template version, you can test your modifications by clicking the "Build template" button. Newly published template versions automatically become the default version selection when creating a workspace.

> **Tip**: By not publishing a version as active, you can try them in a workspace before making it default for everybody in your organization. This is helpful to debug new changes without impacting others.
> **Tip**: Even without publishing a version as active, you can still use it to create a workspace before making it the default for everybody in your organization. This may help you debug new changes without impacting others.

Using the CLI, login to Coder and run the following command to edit a single
template:
Expand Down