You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: .github/CONTRIBUTING.md
+8-6
Original file line number
Diff line number
Diff line change
@@ -9,9 +9,8 @@ Please use the pre-filled template to save time.
9
9
However, don't be put off by this template - other more general issues and suggestions are welcome!
10
10
Contributions to the code are even more welcome ;)
11
11
12
-
:::info
13
-
If you need help using or modifying nf-core/rnavar then the best place to ask is on the nf-core Slack [#rnavar](https://nfcore.slack.com/channels/rnavar) channel ([join our Slack here](https://nf-co.re/join/slack)).
14
-
:::
12
+
> [!NOTE]
13
+
> If you need help using or modifying nf-core/rnavar then the best place to ask is on the nf-core Slack [#rnavar](https://nfcore.slack.com/channels/rnavar) channel ([join our Slack here](https://nf-co.re/join/slack)).
15
14
16
15
## Contribution workflow
17
16
@@ -27,8 +26,11 @@ If you're not used to this workflow with git, you can start with some [docs from
27
26
28
27
## Tests
29
28
30
-
You can optionally test your changes by running the pipeline locally. Then it is recommended to use the `debug` profile to
31
-
receive warnings about process selectors and other debug info. Example: `nextflow run . -profile debug,test,docker --outdir <OUTDIR>`.
29
+
You have the option to test your changes locally by running the pipeline. For receiving warnings about process selectors and other `debug` information, it is recommended to use the debug profile. Execute all the tests with the following command:
30
+
31
+
```bash
32
+
nf-test test --profile debug,test,docker --verbose
33
+
```
32
34
33
35
When you create a pull request with changes, [GitHub Actions](https://github.com/features/actions) will run automatic tests.
34
36
Typically, pull-requests are only fully reviewed when these tests are passing, though of course we can help out before then.
@@ -90,7 +92,7 @@ Once there, use `nf-core schema build` to add to `nextflow_schema.json`.
90
92
91
93
Sensible defaults for process resource requirements (CPUs / memory / time) for a process should be defined in `conf/base.config`. These should generally be specified generic with `withLabel:` selectors so they can be shared across multiple processes/steps of the pipeline. A nf-core standard set of labels that should be followed where possible can be seen in the [nf-core pipeline template](https://github.com/nf-core/tools/blob/master/nf_core/pipeline-template/conf/base.config), which has the default process as a single core-process, and then different levels of multi-core configurations for increasingly large memory requirements defined with standardised labels.
92
94
93
-
The process resources can be passed on to the tool dynamically within the process with the `${task.cpu}` and `${task.memory}` variables in the `script:` block.
95
+
The process resources can be passed on to the tool dynamically within the process with the `${task.cpus}` and `${task.memory}` variables in the `script:` block.
stale-issue-message: "This issue has been tagged as awaiting-changes or awaiting-feedback by an nf-core contributor. Remove stale label or add a comment otherwise this issue will be closed in 20 days."
16
16
stale-pr-message: "This PR has been tagged as awaiting-changes or awaiting-feedback by an nf-core contributor. Remove stale label or add a comment if it is still useful."
0 commit comments