additionalRepositories path resolution when workspaceLocation is modified

Direct Answer

No. A relative checkoutLocation under additionalRepositories resolves against the default workspace root /workspace, not the custom workspaceLocation. Omitting workspaceLocation does not alter this resolution; secondary repositories are still placed under /workspace/<checkoutLocation>.

How the Paths Resolve

When workspaceLocation is set, Gitpod uses it only as the base for the primary repository. Additional repositories are cloned independently and remain anchored to /workspace. For example, with workspaceLocation: /workspace/myapp and checkoutLocation: extra, the secondary repository lands at /workspace/extra, while the main repository sits at /workspace/myapp.

When workspaceLocation is omitted, the default base is /workspace for every repository, so the behavior looks identical. The anchor does not change; it is simply the same as the default.

Making Directory Structures Uniform

If initialization scripts expect all repositories under one base directory, adjust the secondary checkoutLocation so it points inside the custom location:

• Relative escape: ../myapp/extra
• Absolute path: /workspace/myapp/extra

Absolute paths avoid ambiguity during early workspace startup, when the working directory may not yet be /workspace.

Verification

1. Define workspaceLocation: /workspace/myapp and an additionalRepositories entry with checkoutLocation: extra.
2. Start the workspace and run ls /workspace to confirm the extra repository is at /workspace/extra.
3. Update checkoutLocation to ../myapp/extra or /workspace/myapp/extra, restart, and verify with ls /workspace/myapp.
4. Remove workspaceLocation and repeat to confirm the same /workspace-relative placement.

These commands are read-only and scoped to the workspace filesystem.

Version note: This reflects current stable Gitpod configuration semantics. If you are using a self-hosted or pre-release variant, confirm against the latest .gitpod.yml reference.