Skip to content

Add debugger build workflow and README install instructions#581

Merged
rentziass merged 1 commit intodebuggerfrom
copilot/debugger-actions-workflow
Apr 8, 2026
Merged

Add debugger build workflow and README install instructions#581
rentziass merged 1 commit intodebuggerfrom
copilot/debugger-actions-workflow

Conversation

@rentziass
Copy link
Copy Markdown
Member

@rentziass rentziass requested a review from a team as a code owner April 8, 2026 08:45
Copilot AI review requested due to automatic review settings April 8, 2026 08:45
@rentziass rentziass merged commit 53f7bbe into debugger Apr 8, 2026
2 checks passed
@rentziass rentziass deleted the copilot/debugger-actions-workflow branch April 8, 2026 08:45
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds a dedicated GitHub Actions workflow to build and upload a “debugger” VS Code extension VSIX, and documents how to install that build from CI artifacts.

Changes:

  • Add a new debugger-build.yml workflow that packages a debugger extension VSIX and uploads it as an artifact.
  • Add README instructions for downloading and installing the debugger VSIX from the workflow artifacts.
Show a summary per file
File Description
README.md Adds end-user instructions for installing the debugger preview build from workflow artifacts.
.github/workflows/debugger-build.yml Introduces a new CI workflow to package and upload a debugger VSIX artifact.

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

  • Files reviewed: 2/2 changed files
  • Comments generated: 2

@@ -1,5 +1,7 @@
# GitHub Actions for VS Code

> **🐛 Actions Job Debugger (Preview):** To try the latest debugger build, download the `.vsix` artifact from the most recent [Build Debugger Extension](https://github.com/github/vscode-github-actions/actions/workflows/debugger-build.yml) workflow run. On the workflow run page, scroll to **Artifacts** and download **vscode-github-actions-debugger**. Then install it in VS Code by running `code --install-extension <path-to-downloaded.vsix>` or via the Extensions view → `⋯` menu → **Install from VSIX…**.
Copy link

Copilot AI Apr 8, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

GitHub Actions artifacts are downloaded as a .zip file (even when the artifact contains a single .vsix). The current wording suggests downloading a “.vsix artifact” directly; please clarify that users should download the artifact zip and extract the .vsix before running code --install-extension (or installing via VS Code UI).

Suggested change
> **🐛 Actions Job Debugger (Preview):** To try the latest debugger build, download the `.vsix` artifact from the most recent [Build Debugger Extension](https://github.com/github/vscode-github-actions/actions/workflows/debugger-build.yml) workflow run. On the workflow run page, scroll to **Artifacts** and download **vscode-github-actions-debugger**. Then install it in VS Code by running `code --install-extension <path-to-downloaded.vsix>` or via the Extensions view → `` menu → **Install from VSIX…**.
> **🐛 Actions Job Debugger (Preview):** To try the latest debugger build, go to the most recent [Build Debugger Extension](https://github.com/github/vscode-github-actions/actions/workflows/debugger-build.yml) workflow run. On the workflow run page, scroll to **Artifacts** and download **vscode-github-actions-debugger**. GitHub Actions artifacts download as a `.zip` file, so extract the contained `.vsix` file first, then install it in VS Code by running `code --install-extension <path-to-extracted.vsix>` or via the Extensions view → `` menu → **Install from VSIX…**.

Copilot uses AI. Check for mistakes.
Comment on lines +31 to +37
- name: Create a package.json without scoped name
run: |
cp package.json package.json.real
sed --regexp-extended '/"name"\s*:/ s#@[a-zA-Z\\-]+/##' package.json.real > package.json

- run: npm run package

Copy link

Copilot AI Apr 8, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This step leaves a temporary package.json.real in the workspace. Since vsce package includes files unless excluded by .vscodeignore/files, the generated VSIX will likely contain package.json.real as an extra file. Consider deleting the temp file before packaging or writing it to a temp location, or explicitly excluding it in .vscodeignore.

Suggested change
- name: Create a package.json without scoped name
run: |
cp package.json package.json.real
sed --regexp-extended '/"name"\s*:/ s#@[a-zA-Z\\-]+/##' package.json.real > package.json
- run: npm run package
- name: Create a package.json without scoped name and package extension
run: |
TEMP_PACKAGE_JSON="$RUNNER_TEMP/package.json.real"
cp package.json "$TEMP_PACKAGE_JSON"
cleanup() {
cp "$TEMP_PACKAGE_JSON" package.json
rm -f "$TEMP_PACKAGE_JSON"
}
trap cleanup EXIT
sed --regexp-extended '/"name"\s*:/ s#@[a-zA-Z\\-]+/##' "$TEMP_PACKAGE_JSON" > package.json
npm run package

Copilot uses AI. Check for mistakes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants