Skip to content
CI

fix: handle category-related changes after importing a config more elegantly #1229

Sign in to view logs

fix: handle category-related changes after importing a config more elegantly

fix: handle category-related changes after importing a config more elegantly #1229

Triggered via pull request September 12, 2024 19:58
@achou11achou11
synchronize #687
686/obs-preset-unknown
Status Success
Total duration 1m 6s
Artifacts –

ci.yml

on: pull_request
all
43s
all
backend
11s
backend
frontend
57s
frontend
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
backend
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
all
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
frontend
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/