Back-merge the 4.0.3 security patch into dev - #168
Conversation
This pipeline's TEMPLATE branch never received the nf-core/tools 4.0.3 sync, so the patch was taken from nf-core/abotyper's TEMPLATE branch with the repository identity in branch.yml rewritten for this pipeline. That identity is the only pipeline-specific content the template renders into any of the patched workflows, so this is the same change this pipeline's own sync would have produced — but the substituted source is worth a look. These files conflicted with the patch and were reset wholesale to the nf-core/tools 4.0.3 template version, on the basis that they carry no pipeline-specific content. If this branch had local edits in them, those edits are gone — please review: .github/workflows/branch.yml .github/workflows/linting.yml
Remove vulnerable PR-comment artifact pattern
YAML linting is failingTo keep the code consistent with lots of contributors, we run automated code consistency checks.
Once you push these changes the test should pass, and you can hide this comment 👍 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! |
Markdown linting is failingTo keep the code consistent with lots of contributors, we run automated code consistency checks.
Once you push these changes the test should pass, and you can hide this comment 👍 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! |
Forward-ports the merged
mastersecurity patch intodevso the fix is a shared ancestor and the coming removal of the momentarily ignored lint tests (coming with nf-core/tools 4.1.0) propagates cleanly.