Skip to content
ci

Added hints on how to make the KLighD VS Code extension debuggable from the launch configurations. #40

Sign in to view logs

Added hints on how to make the KLighD VS Code extension debuggable from the launch configurations.

Added hints on how to make the KLighD VS Code extension debuggable from the launch configurations. #40

Triggered via pull request October 22, 2024 15:22
@NiklasRentzCAUNiklasRentzCAU
opened #101
nre/how-to-debug-klighd
Status Success
Total duration 3m 20s
Artifacts 1

ci.yml

on: pull_request
Run eslint and test and build
3m 9s
Run eslint and test and build
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
Run eslint and test and build
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-node@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Run eslint and test and build
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/cache@v3, actions/setup-node@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Artifacts

Produced during runtime
Name Size
KIELER VS Code Extension (no server)
133 KB