Skip to content

Commit 878a3e6

Browse files
authored
Merge pull request #1141 from nf-core/nf-core-template-merge-2.11
Important! Template update for nf-core/tools v2.11
2 parents e4c8d67 + 2e72110 commit 878a3e6

File tree

16 files changed

+54
-48
lines changed

16 files changed

+54
-48
lines changed

.github/CONTRIBUTING.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -27,6 +27,9 @@ If you're not used to this workflow with git, you can start with some [docs from
2727

2828
## Tests
2929

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>`.
32+
3033
When you create a pull request with changes, [GitHub Actions](https://github.com/features/actions) will run automatic tests.
3134
Typically, pull-requests are only fully reviewed when these tests are passing, though of course we can help out before then.
3235

.github/PULL_REQUEST_TEMPLATE.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -19,6 +19,7 @@ Learn more about contributing: [CONTRIBUTING.md](https://github.com/nf-core/rnas
1919
- [ ] If necessary, also make a PR on the nf-core/rnaseq _branch_ on the [nf-core/test-datasets](https://github.com/nf-core/test-datasets) repository.
2020
- [ ] Make sure your code lints (`nf-core lint`).
2121
- [ ] Ensure the test suite passes (`nextflow run . -profile test,docker --outdir <OUTDIR>`).
22+
- [ ] Check for unexpected warnings in debug mode (`nextflow run . -profile debug,test,docker --outdir <OUTDIR>`).
2223
- [ ] Usage Documentation in `docs/usage.md` is updated.
2324
- [ ] Output Documentation in `docs/output.md` is updated.
2425
- [ ] `CHANGELOG.md` is updated.

.github/workflows/ci.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ jobs:
2828
- "latest-everything"
2929
steps:
3030
- name: Check out pipeline code
31-
uses: actions/checkout@v3
31+
uses: actions/checkout@v4
3232

3333
- name: Install Nextflow
3434
uses: nf-core/setup-nextflow@v1

.github/workflows/fix-linting.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ jobs:
1313
runs-on: ubuntu-latest
1414
steps:
1515
# Use the @nf-core-bot token to check out so we can push later
16-
- uses: actions/checkout@v3
16+
- uses: actions/checkout@v4
1717
with:
1818
token: ${{ secrets.nf_core_bot_auth_token }}
1919

@@ -24,7 +24,7 @@ jobs:
2424
env:
2525
GITHUB_TOKEN: ${{ secrets.nf_core_bot_auth_token }}
2626

27-
- uses: actions/setup-node@v3
27+
- uses: actions/setup-node@v4
2828

2929
- name: Install Prettier
3030
run: npm install -g prettier @prettier/plugin-php

.github/workflows/linting.yml

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -14,9 +14,9 @@ jobs:
1414
EditorConfig:
1515
runs-on: ubuntu-latest
1616
steps:
17-
- uses: actions/checkout@v3
17+
- uses: actions/checkout@v4
1818

19-
- uses: actions/setup-node@v3
19+
- uses: actions/setup-node@v4
2020

2121
- name: Install editorconfig-checker
2222
run: npm install -g editorconfig-checker
@@ -27,9 +27,9 @@ jobs:
2727
Prettier:
2828
runs-on: ubuntu-latest
2929
steps:
30-
- uses: actions/checkout@v3
30+
- uses: actions/checkout@v4
3131

32-
- uses: actions/setup-node@v3
32+
- uses: actions/setup-node@v4
3333

3434
- name: Install Prettier
3535
run: npm install -g prettier
@@ -40,7 +40,7 @@ jobs:
4040
PythonBlack:
4141
runs-on: ubuntu-latest
4242
steps:
43-
- uses: actions/checkout@v3
43+
- uses: actions/checkout@v4
4444

4545
- name: Check code lints with Black
4646
uses: psf/black@stable
@@ -71,7 +71,7 @@ jobs:
7171
runs-on: ubuntu-latest
7272
steps:
7373
- name: Check out pipeline code
74-
uses: actions/checkout@v3
74+
uses: actions/checkout@v4
7575

7676
- name: Install Nextflow
7777
uses: nf-core/setup-nextflow@v1

.gitpod.yml

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,9 @@ tasks:
44
command: |
55
pre-commit install --install-hooks
66
nextflow self-update
7-
7+
- name: unset JAVA_TOOL_OPTIONS
8+
command: |
9+
unset JAVA_TOOL_OPTIONS
810
vscode:
911
extensions: # based on nf-core.nf-core-extensionpack
1012
- codezombiech.gitignore # Language support for .gitignore files

README.md

Lines changed: 5 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -50,11 +50,8 @@
5050
5151
## Usage
5252

53-
:::note
54-
If you are new to Nextflow and nf-core, please refer to [this page](https://nf-co.re/docs/usage/installation) on how
55-
to set-up Nextflow. Make sure to [test your setup](https://nf-co.re/docs/usage/introduction#how-to-run-a-pipeline)
56-
with `-profile test` before running the workflow on actual data.
57-
:::
53+
> [!NOTE]
54+
> If you are new to Nextflow and nf-core, please refer to [this page](https://nf-co.re/docs/usage/installation) on how to set-up Nextflow. Make sure to [test your setup](https://nf-co.re/docs/usage/introduction#how-to-run-a-pipeline) with `-profile test` before running the workflow on actual data.
5855
5956
First, prepare a samplesheet with your input data that looks as follows:
6057

@@ -84,11 +81,9 @@ nextflow run nf-core/rnaseq \
8481
-profile <docker/singularity/.../institute>
8582
```
8683

87-
:::warning
88-
Please provide pipeline parameters via the CLI or Nextflow `-params-file` option. Custom config files including those
89-
provided by the `-c` Nextflow option can be used to provide any configuration _**except for parameters**_;
90-
see [docs](https://nf-co.re/usage/configuration#custom-configuration-files).
91-
:::
84+
> [!WARNING]
85+
> Please provide pipeline parameters via the CLI or Nextflow `-params-file` option. Custom config files including those provided by the `-c` Nextflow option can be used to provide any configuration _**except for parameters**_;
86+
> see [docs](https://nf-co.re/usage/configuration#custom-configuration-files).
9287
9388
For more details and further functionality, please refer to the [usage documentation](https://nf-co.re/rnaseq/usage) and the [parameter documentation](https://nf-co.re/rnaseq/parameters).
9489

assets/multiqc_config.yml

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,5 @@
11
report_comment: >
2-
This report has been generated by the <a href="https://github.com/nf-core/rnaseq/releases/tag/3.13.0" target="_blank">nf-core/rnaseq</a>
3-
analysis pipeline. For information about how to interpret these results, please see the
4-
<a href="https://nf-co.re/rnaseq/3.13.0/docs/output" target="_blank">documentation</a>.
2+
This report has been generated by the <a href="https://github.com/nf-core/rnaseq/tree/dev" target="_blank">nf-core/rnaseq</a> analysis pipeline. For information about how to interpret these results, please see the <a href="https://nf-co.re/rnaseq/3.13.0/docs/output" target="_blank">documentation</a>.
53
report_section_order:
64
"nf-core-rnaseq-methods-description":
75
order: -1000

docs/usage.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ You will need to create a samplesheet with information about the samples you wou
2020

2121
The `sample` identifiers have to be the same when you have re-sequenced the same sample more than once e.g. to increase sequencing depth. The pipeline will concatenate the raw reads before performing any downstream analysis. Below is an example for the same sample sequenced across 3 lanes. If you set the strandedness value to `auto` the pipeline will sub-sample the input FastQ files to 1 million reads, use Salmon Quant to infer the strandedness automatically and then propagate this information to the remainder of the pipeline. If the strandedness has been inferred or provided incorrectly a warning will be present at the top of the MultiQC report so please be sure to check when looking at the QC for your samples.
2222

23-
```console
23+
```csv title="samplesheet.csv"
2424
sample,fastq_1,fastq_2,strandedness
2525
CONTROL_REP1,AEG588A1_S1_L002_R1_001.fastq.gz,AEG588A1_S1_L002_R2_001.fastq.gz,auto
2626
CONTROL_REP1,AEG588A1_S1_L003_R1_001.fastq.gz,AEG588A1_S1_L003_R2_001.fastq.gz,auto
@@ -33,7 +33,7 @@ The pipeline will auto-detect whether a sample is single- or paired-end using th
3333

3434
A final samplesheet file consisting of both single- and paired-end data may look something like the one below. This is for 6 samples, where `TREATMENT_REP3` has been sequenced twice.
3535

36-
```console
36+
```csv title="samplesheet.csv"
3737
sample,fastq_1,fastq_2,strandedness
3838
CONTROL_REP1,AEG588A1_S1_L002_R1_001.fastq.gz,AEG588A1_S1_L002_R2_001.fastq.gz,forward
3939
CONTROL_REP2,AEG588A2_S2_L002_R1_001.fastq.gz,AEG588A2_S2_L002_R2_001.fastq.gz,forward

0 commit comments

Comments
 (0)