meta(vscode): Add pipeline to test and build private feature vsix #6427
Conversation
| workflow_dispatch: # Trigger only manually workflow_dispatch: # Trigger only manually | ||
|
|
||
| env: | ||
| AI_KEY: 3cf0d6ae-3327-414a-b7c1-12f31ef45eff |
There was a problem hiding this comment.
is this a secret? should we be storing it in source?
There was a problem hiding this comment.
especially on open source github
There was a problem hiding this comment.
The AI key is not a secret, we already have it in the repo, according to the telemetry package that vscode offers is not sensitive
The AI key is not a secret; it’s already in the repository. According to the telemetry package provided by VS Code, it is not considered sensitive information. For more details, you can refer to the VS Code extension telemetry documentation.
There was a problem hiding this comment.
I would say we should still add this to a variable in case we need to change it in future. Will be handy without changing the code. If it is not a secret, the value can be set as a variable instead of secret
ccastrotrejo
changed the title
This pull request introduces a new GitHub Actions workflow to automate the building and testing of a private VSIX (Visual Studio Code extension) package. The workflow is designed to run tests on different Node.js versions and build the VSIX package with specific configurations.
Why having new pipeline
The idea is to have a pipeline in which creates a VSIX that closely resembles a release version. This pipeline requires a branch name as input, runs the tests, and builds the VSIX in GitHub. As a result, we will be able to distribute a more solid private vsix
New GitHub Actions Workflow:
testandbuild. Thetestjob runs on multiple Node.js versions (18.x, 20.x, 22.x) and caches the turbo build setup. Thebuildjob sets up Node.js version 20, replaces placeholders with the telemetry key, and packs the VSCode Designer Extension.