Skip to content

Remove fusion retrieval to circumvent failures with nested config imports #234

Remove fusion retrieval to circumvent failures with nested config imports

Remove fusion retrieval to circumvent failures with nested config imports #234

Triggered via pull request July 26, 2024 08:19
Status Success
Total duration 1m 11s
Artifacts 1

linting.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Prettier
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, 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/
PythonBlack
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
EditorConfig
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, 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/
nf-core
The following actions uses Node.js version which is deprecated and will be forced to run on node20: nf-core/setup-nextflow@v1. 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
linting-logs Expired
6.26 KB