Skip to content

docs: use colons as task name separators in examples#3028

Merged
bartlomieju merged 1 commit into
mainfrom
docs/task-colon-naming
May 21, 2026
Merged

docs: use colons as task name separators in examples#3028
bartlomieju merged 1 commit into
mainfrom
docs/task-colon-naming

Conversation

@bartlomieju
Copy link
Copy Markdown
Member

@bartlomieju bartlomieju commented Apr 8, 2026

Updates the task naming examples in runtime/reference/cli/task.md to use : as the separator (e.g. build:client, dev:server) instead of -, bringing this page in line with the rest of the docs, which already use the colon convention (test:all, build:full, dev:api, lint:fix, etc.). Adds a short note explicitly recommending : for multi-word task names — answering the question raised in #2989 — and incidentally fixes a preexisting "sever" typo in the dev-server example.

Ref #2989

Copy link
Copy Markdown
Contributor

@lunadogbot lunadogbot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mechanical rename to colon-separated task names; CI green.

  • nit: line 214 still has sever/mod.ts — pre-existing typo, but you're touching that exact line so it's easy to fix in this PR.

Updates task naming examples to use colons (e.g. `build:client`,
`dev:server`) instead of hyphens, following the convention used in
the npm ecosystem and the rest of the Deno docs. Adds a short note
recommending the colon separator, and fixes an existing typo
("sever" → "server") in the dev-server example.

Ref #2989
@bartlomieju bartlomieju force-pushed the docs/task-colon-naming branch from 9e25164 to 250ebcf Compare May 21, 2026 10:44
@bartlomieju bartlomieju merged commit ed6a2fe into main May 21, 2026
0 of 2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants