Closed pditommaso closed 1 week ago
Name | Link |
---|---|
Latest commit | 65e3eb2da4da35f15cafd1310ec6e47b4dcbe22c |
Latest deploy log | https://app.netlify.com/sites/nextflow-docs-staging/deploys/66701cca7fc5a700082a8492 |
Deploy Preview | https://deploy-preview-5071--nextflow-docs-staging.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
I would suggest exposing it as nextflow.failOnIgnore
so as to not confuse it with feature flags. Long term I don't think we should allow feature flags in the config because they are inherent to the pipeline code.
In other words:
nextflow
config scope is used for runtime options and is only relevant in the config fileThat was the first option, but then I realised it's not a feature flag but more a workflow (error handling) behaviour, and as such reported in the workflow metadata
Let's go
This PR implements the fail on ignore by using by setting the option
nextflow.enable.failOnIgnore
in the nextflow config file.