Skip to content
Linting and tests

add an option of larpix fee config as a constant in yaml #541

Sign in to view logs

add an option of larpix fee config as a constant in yaml

add an option of larpix fee config as a constant in yaml #541

Triggered via pull request September 15, 2024 07:27
@YifanCYifanC
opened #141
feature_config
Status Success
Total duration 7m 55s
Artifacts –

test.yml

on: pull_request
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
build (0)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (0)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, conda-incubator/setup-miniconda@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build (1)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (1)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, conda-incubator/setup-miniconda@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/