Skip to content

docs: record Linux build validation success #6

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
tariqsaidofficial merged 1 commit into from
Jun 9, 2026
Merged

docs: record Linux build validation success #6

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 20 additions & 0 deletions docs/wpcodespace-build-validation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,3 +51,23 @@ The next validation phase should verify:
- Do not patch nls.messages.js.
- Do not treat the failed local macOS build as a product runtime failure.
- Do not proceed to WPCodeSpace Docker image consumption until a Linux/CI build path passes.

## Linux CI validation success

The WPCodeSpace OpenVSCode Linux build validation workflow has passed after adding the required native Linux build dependencies.

Validated in GitHub Actions on Linux:

- npm ci
- npm run compile-web
- no tracked generated workbench.js or nls.messages patching required

This establishes Linux CI as the supported validation path for WPCodeSpace OpenVSCode source customization.

Next validation phase:

1. Identify the correct OpenVSCode server/image build command.
2. Produce a pinned WPCodeSpace OpenVSCode image from this fork.
3. Run the image locally.
4. Verify the WPCodeSpace Chat copy appears in the running OpenVSCode Chat panel.
5. Only then update the WPCodeSpace repo to consume the pinned image.
Loading