Closed nictru closed 3 months ago
To keep the code consistent with lots of contributors, we run automated code consistency checks. To fix this CI test, please run:
yaml-lint
npm
then install yaml-lint
(npm install -g yaml-lint
)yamllint $(find . -type f -name "*.yml" -o -name "*.yaml")
Once you push these changes the test should pass, and you can hide this comment :+1:
We highly recommend setting up yaml-lint in your code editor so that this formatting is done automatically on save. Ask about it on Slack for help!
Thanks again for your contribution!
To keep the code consistent with lots of contributors, we run automated code consistency checks. To fix this CI test, please run:
markdownlint-cli
brew install markdownlint-cli
npm
then install markdownlint-cli
(npm install -g markdownlint-cli
)markdownlint . --fix
markdownlint .
Once you push these changes the test should pass, and you can hide this comment :+1:
We highly recommend setting up markdownlint in your code editor so that this formatting is done automatically on save. Ask about it on Slack for help!
Thanks again for your contribution!
@nf-core-bot fix linting pretty please :pray:
Do we still have to make sure the CI passes in this situation?
Do we still have to make sure the CI passes in this situation?
not really, but I like nice things
As discussed in the #scflow slack channel, this PR adds a deprecation notice to the Repo Readme.
I did not find any good examples in other archived pipelines since the archiving adds similar notices. An example can be found here