github-actions-vscode-ci

GitHub Actions CI for VS Code extensions uses `xvfb-run -a npm test` to execute extension tests in a headless Linux environment, ensuring reliable automated testing without a physical display.

VS Code extension tests fail on Linux CI environments because they require a display server. The Skill uses `xvfb-run` to provide a virtual display buffer, allowing the extension host to initialize and run tests successfully.

Yes, you can cancel redundant GitHub Actions builds for the same pull request by implementing concurrency control in your workflow, which automatically cancels previous in-progress runs when new code is pushed, saving CI resources.

The best way to manage dependencies in GitHub Actions for VS Code extensions is using `npm ci` instead of `npm install`. This ensures clean, reproducible, and faster dependency installation by leveraging the package-lock.json file.

Common anti-patterns when optimizing GitHub Actions CI include lacking concurrency control for pull request builds, using `npm install` instead of `npm ci`, and failing to use `xvfb-run` for headless VS Code extension testing.