From 8ddd47cffc2b3d352fdea35bf8ba7ae2fcf257d4 Mon Sep 17 00:00:00 2001 From: Samuel K Date: Thu, 22 Oct 2026 00:15:08 -0600 Subject: [PATCH] docs(devcontainer): use --devcontainer flag in workspace up example devsy workspace up does not register --devcontainer-path; only workspace build does. Verified via go run . workspace up --help, which lists --devcontainer and no --devcontainer-path. --- .../content/docs/developing-in-workspaces/devcontainer-json.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sites/docs-devsy-sh/content/docs/developing-in-workspaces/devcontainer-json.mdx b/sites/docs-devsy-sh/content/docs/developing-in-workspaces/devcontainer-json.mdx index 4d296f6d73..6052326f5f 100644 --- a/sites/docs-devsy-sh/content/docs/developing-in-workspaces/devcontainer-json.mdx +++ b/sites/docs-devsy-sh/content/docs/developing-in-workspaces/devcontainer-json.mdx @@ -20,7 +20,7 @@ Devsy looks for one of: To use a specific file, pass its path: ```sh -devsy workspace up github.com/my-org/my-repo --devcontainer-path ./path/to/devcontainer.json +devsy workspace up github.com/my-org/my-repo --devcontainer ./path/to/devcontainer.json ``` A configuration can inherit from other files with `extends`, which takes a path or a list of paths. Keep files the configuration depends on inside its folder.