From 056f019c66f5d5b76ecdf951d854bbd3b8ced71a Mon Sep 17 00:00:00 2001 From: "devsy-app[bot]" <277138668+devsy-app[bot]@users.noreply.github.com> Date: Sat, 15 Aug 2026 12:45:39 +0000 Subject: [PATCH] docs: fix devsy build command reference MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit ## Doc area `sites/docs-devsy-sh/content/docs/developing-in-workspaces/continuous-integration.mdx` — the "Pre-building and pushing images" section. ## Drift found The docs referenced `devsy build` as the command to pre-build and publish a devcontainer image: ```sh devsy build --repository ghcr.io/my-org/my-devcontainer --tag latest --push ``` `build` is not a top-level command. In `cmd/root.go`, the registered root subcommands are `ci`, `config`, `context`, `env`, `feature`, `ide`, `machine`, `mcp`, `provider`, `secrets`, `snapshot`, `template`, `update`, `workspace`, and `internal`. There is no top-level `build` command, so `devsy build ...` would fail with "unknown command". `build` is a subcommand of `workspace` (`cmd/workspace/workspace.go` registers `NewBuildCmd`, `cmd/workspace/build.go` defines `Use: "build [flags] [workspace-path|workspace-name]"`). ## Correction Changed both the prose and the code sample to use `devsy workspace build`: ```sh devsy workspace build --repository ghcr.io/my-org/my-devcontainer --tag latest --push ``` ## Code verification performed - Confirmed `cmd/root.go` root subcommand list has no top-level `build`. - Confirmed `cmd/workspace/workspace.go:25` calls `cmd.AddCommand(NewBuildCmd(globalFlags))` and `cmd/workspace/build.go:40` defines the `build` subcommand. - Confirmed the documented flags exist for `devsy workspace build` in `cmd/workspace/build.go` `registerImageFlags`: `--repository` (`names.Repository`), `--tag` (`names.Tag`), and `--push` (`names.Push`) — all present in `pkg/flags/names/names.go`. - Checked open PRs; none address this drift. ## Verification (formatting gate) - `task cli:format` — clean. - `task cli:lint:ci` — 0 issues. - `task cli:test` — only the known pre-existing `pkg/git` `TestRepoClone*` failures (a stale assertion on `origin/main`, not caused by this docs-only change). No new failures introduced. This PR was created by an AI agent as part of an automated daily docs job. --- .../docs/developing-in-workspaces/continuous-integration.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/sites/docs-devsy-sh/content/docs/developing-in-workspaces/continuous-integration.mdx b/sites/docs-devsy-sh/content/docs/developing-in-workspaces/continuous-integration.mdx index 7dcc2deb37..5983b54d5d 100644 --- a/sites/docs-devsy-sh/content/docs/developing-in-workspaces/continuous-integration.mdx +++ b/sites/docs-devsy-sh/content/docs/developing-in-workspaces/continuous-integration.mdx @@ -77,10 +77,10 @@ devsy ci --keep -- ./run-integration-tests.sh ### Pre-building and pushing images `devsy ci` focuses on running a command. To pre-build and publish a devcontainer -image for reuse as a build cache, use `devsy build`: +image for reuse as a build cache, use `devsy workspace build`: ```sh -devsy build --repository ghcr.io/my-org/my-devcontainer --tag latest --push +devsy workspace build --repository ghcr.io/my-org/my-devcontainer --tag latest --push ``` Downstream CI jobs can then reference that image via `--cache-from` to speed up