docs(templates): add variable vs coder_parameter guidance, deprecated fields, registry PR conventions#3
Merged
DevelopmentCats merged 3 commits intoJun 3, 2026
Conversation
… fields, registry PR conventions
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds three sections to the templates skill based on patterns that come up when building real templates against a homelab Coder deployment.
Changes
variablevscoder_parameter— clarifies when each should be used. Infrastructure-level choices fixed per deployment (host arch, storage pool, remote host) belong invariableand are set by the admin at push time. Per-workspace choices (image, cpu, memory) belong incoder_parameter. Includes a concrete example and the push command with--variable.Deprecated
coder_agentfields —diris deprecated in recent provider versions, generates warnings on everycoder templates push, and breaks Coder Desktop file sync. Worth calling out explicitly since it appears in older templates that get copied as a starting point.Contributing templates to
coder/registry— links toAGENTS.mdand the PR template rather than duplicating them, and adds three non-obvious gotchas: no.tftest.hclrequired for templates, the PR title convention (feat(<namespace>/templates/<name>): ...), and syncing the fork'smainwith upstream before branching to avoid a noisy diff.Type of Change