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/workflows/branch.yml
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ jobs:
24
24
message: |
25
25
Hi @${{ github.event.pull_request.user.login }},
26
26
27
-
It looks like this pull-request has been made against the ${{github.event.pull_request.head.repo.full_name}} `master` branch. The `master` branch on nf-core repositories should always contain code from the latest release. Beacuse of this, PRs to `master` are only allowed if they come from the ${{github.event.pull_request.head.repo.full_name}} `dev` branch.
27
+
It looks like this pull-request has been made against the ${{github.event.pull_request.head.repo.full_name}} `master` branch. The `master` branch on nf-core repositories should always contain code from the latest release. Because of this, PRs to `master` are only allowed if they come from the ${{github.event.pull_request.head.repo.full_name}} `dev` branch.
28
28
29
29
You do not need to close this PR, you can change the target branch to `dev` by clicking the _"Edit"_ button at the top of this page.
Copy file name to clipboardExpand all lines: docs/lint_errors.md
+26-12Lines changed: 26 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,8 +10,8 @@ The lint test looks for the following required files:
10
10
11
11
*`nextflow.config`
12
12
* The main nextflow config file
13
-
*`Dockerfile`
14
-
* A docker build script to generate a docker image with the required software
13
+
*`nextflow_schema.json`
14
+
* A JSON schema describing pipeline parameters, generated using `nf-core schema build`
15
15
* Continuous integration tests with [GitHub Actions](https://github.com/features/actions)
16
16
* GitHub Actions workflows for CI of your pipeline (`.github/workflows/ci.yml`), branch protection (`.github/workflows/branch.yml`) and nf-core best practice linting (`.github/workflows/linting.yml`)
17
17
*`LICENSE`, `LICENSE.md`, `LICENCE.md` or `LICENCE.md`
@@ -27,8 +27,14 @@ The following files are suggested but not a hard requirement. If they are missin
27
27
28
28
*`main.nf`
29
29
* It's recommended that the main workflow script is called `main.nf`
30
+
*`environment.yml`
31
+
* A conda environment file describing the required software
32
+
*`Dockerfile`
33
+
* A docker build script to generate a docker image with the required software
30
34
*`conf/base.config`
31
35
* A `conf` directory with at least one config called `base.config`
36
+
*`.github/workflows/awstest.yml` and `.github/workflows/awsfulltest.yml`
37
+
* GitHub workflow scripts used for automated tests on AWS
32
38
33
39
The following files will cause a failure if the _are_ present (to fix, delete them):
34
40
@@ -39,13 +45,18 @@ The following files will cause a failure if the _are_ present (to fix, delete th
39
45
*`parameters.settings.json`
40
46
* The syntax for pipeline schema has changed - old `parameters.settings.json` should be
41
47
deleted and new `nextflow_schema.json` files created instead.
48
+
*`bin/markdown_to_html.r`
49
+
* The old markdown to HTML conversion script, now replaced by `markdown_to_html.py`
42
50
43
51
## Error #2 - Docker file check failed ## {#2}
44
52
45
-
Pipelines should have a files called `Dockerfile` in their root directory.
53
+
DSL1 pipelines should have a file called `Dockerfile` in their root directory.
46
54
The file is used for automated docker image builds. This test checks that the file
47
55
exists and contains at least the string `FROM` (`Dockerfile`).
48
56
57
+
Some pipelines, especially DSL2, may not have a `Dockerfile`. In this case a warning
58
+
will be generated which can be safely ignored.
59
+
49
60
## Error #3 - Licence check failed ## {#3}
50
61
51
62
nf-core pipelines must ship with an open source [MIT licence](https://choosealicense.com/licenses/mit/).
@@ -216,22 +227,25 @@ This test will fail if the following requirements are not met in these files:
4. `awstest.yml`: Triggers tests on AWS batch. As running tests on AWS incurs costs, they should be only triggered on `push` to `master` and `release`.
220
-
* Must be turned on for `push` to `master` and `release`.
221
-
* Must not be turned on for `pull_request` or other events.
230
+
4. `awstest.yml`: Triggers tests on AWS batch. As running tests on AWS incurs costs, they should be only triggered on `workflow_dispatch`.
231
+
This allows for manual triggering of the workflow when testing on AWS is desired.
232
+
You can trigger the tests by going to the `Actions` tab on the pipeline GitHub repository and selecting the `nf-core AWS test` workflow on the left.
233
+
* Must not be turned on for `push` or `pull_request`.
234
+
* Must be turned on for `workflow_dispatch`.
222
235
223
236
### GitHub Actions AWS full tests
224
237
225
238
Additionally, we provide the possibility of testing the pipeline on full size datasets on AWS.
226
239
This should ensure that the pipeline runs as expected on AWS and provide a resource estimation.
227
-
The GitHub Actions workflow is: `awsfulltest.yml`, and it can be found in the `.github/workflows/` directory.
228
-
This workflow incurrs higher AWS costs, therefore it should only be triggered on `release`.
229
-
For tests on full data prior to release, [https://tower.nf](Nextflow Tower's launch feature) can be employed.
240
+
The GitHub Actions workflow is `awsfulltest.yml`, and it can be found in the `.github/workflows/` directory.
241
+
This workflow incurrs higher AWS costs, therefore it should only be triggered on `release` and `workflow_dispatch`.
242
+
You can trigger the tests by going to the `Actions` tab on the pipeline GitHub repository and selecting the `nf-core AWS full size tests` workflow on the left.
243
+
For tests on full data prior to release, [Nextflow Tower](https://tower.nf) launch feature can be employed.
230
244
231
245
`awsfulltest.yml`: Triggers full sized tests run on AWS batch after releasing.
232
246
233
-
* Must be only turned on for `release`.
234
-
* Should run the profile `test_full`. If it runs the profile `test` a warning is given.
247
+
* Must be only turned on for `release` and `workflow_dispatch`.
248
+
* Should run the profile `test_full` that should be edited to provide the links to full-size datasets. If it runs the profile `test` a warning is given.
0 commit comments