Skip to content

feat: vscode-workbench extension#9

Merged
Vtec234 merged 6 commits intomainfrom
vscode-workbench
May 5, 2026
Merged

feat: vscode-workbench extension#9
Vtec234 merged 6 commits intomainfrom
vscode-workbench

Conversation

@Vtec234
Copy link
Copy Markdown
Member

@Vtec234 Vtec234 commented Apr 28, 2026

  • Add a VSCode extension to integrate it with the workbench.
  • Add a launch target and server endpoint to debug the extension.

Comment thread Makefile
@@ -28,12 +31,21 @@ DOCKER_RUN = docker run --rm --init --interactive --tty \

serve: container
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

we think this Makefile target is no longer needed

Copy link
Copy Markdown
Member Author

@Vtec234 Vtec234 May 4, 2026

Choose a reason for hiding this comment

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

Actually I take this back, it can be useful to check that everything works in prod without using install.sh. Let's keep it?

Copy link
Copy Markdown
Collaborator

@jcreedcmu jcreedcmu left a comment

Choose a reason for hiding this comment

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

We expect CI is fixed after rebasing.

@Vtec234 Vtec234 force-pushed the vscode-workbench branch from 52e5132 to b78de74 Compare May 4, 2026 23:05
@Vtec234 Vtec234 merged commit 13be6dd into main May 5, 2026
1 check passed
@Vtec234 Vtec234 deleted the vscode-workbench branch May 5, 2026 02:58
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.

2 participants