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
+6-6
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
# nf-core/viralrecon: Contributing Guidelines
1
+
# `nf-core/viralrecon`: Contributing Guidelines
2
2
3
3
Hi there!
4
4
Many thanks for taking an interest in improving nf-core/viralrecon.
@@ -55,23 +55,23 @@ These tests are run both with the latest available version of `Nextflow` and als
55
55
56
56
:warning: Only in the unlikely and regretful event of a release happening with a bug.
57
57
58
-
- On your own fork, make a new branch `patch` based on `upstream/master`.
58
+
- On your own fork, make a new branch `patch` based on `upstream/main` or `upstream/master`.
59
59
- Fix the bug, and bump version (X.Y.Z+1).
60
-
-A PR should be made on `master`from patch to directly this particular bug.
60
+
-Open a pull-request from `patch` to `main`/`master`with the changes.
61
61
62
62
## Getting help
63
63
64
64
For further information/help, please consult the [nf-core/viralrecon documentation](https://nf-co.re/viralrecon/usage) and don't hesitate to get in touch on the nf-core Slack [#viralrecon](https://nfcore.slack.com/channels/viralrecon) channel ([join our Slack here](https://nf-co.re/join/slack)).
65
65
66
66
## Pipeline contribution conventions
67
67
68
-
To make the nf-core/viralrecon code and processing logic more understandable for new contributors and to ensure quality, we semi-standardise the way the code and other contributions are written.
68
+
To make the `nf-core/viralrecon` code and processing logic more understandable for new contributors and to ensure quality, we semi-standardise the way the code and other contributions are written.
69
69
70
70
### Adding a new step
71
71
72
72
If you wish to contribute a new step, please use the following coding standards:
73
73
74
-
1. Define the corresponding input channel into your new process from the expected previous process channel
74
+
1. Define the corresponding input channel into your new process from the expected previous process channel.
75
75
2. Write the process block (see below).
76
76
3. Define the output channel if needed (see below).
77
77
4. Add any new parameters to `nextflow.config` with a default (see below).
@@ -84,7 +84,7 @@ If you wish to contribute a new step, please use the following coding standards:
84
84
85
85
### Default values
86
86
87
-
Parameters should be initialised / defined with default values in `nextflow.config` under the `params` scope.
87
+
Parameters should be initialised / defined with default values within the `params` scope in `nextflow.config`.
88
88
89
89
Once there, use `nf-core pipelines schema build` to add to `nextflow_schema.json`.
## This PR is against the `${{github.event.pull_request.base.ref}}` branch :x:
26
28
27
29
* Do not close this PR
28
30
* Click _Edit_ and change the `base` to `dev`
@@ -32,9 +34,9 @@ jobs:
32
34
33
35
Hi @${{ github.event.pull_request.user.login }},
34
36
35
-
It looks like this pull-request is has been made against the [${{github.event.pull_request.head.repo.full_name }}](https://github.com/${{github.event.pull_request.head.repo.full_name }}) `master` branch.
36
-
The `master` branch on nf-core repositories should always contain code from the latest release.
37
-
Because of this, PRs to `master` are only allowed if they come from the [${{github.event.pull_request.head.repo.full_name }}](https://github.com/${{github.event.pull_request.head.repo.full_name }}) `dev` branch.
37
+
It looks like this pull-request is has been made against the [${{github.event.pull_request.head.repo.full_name }}](https://github.com/${{github.event.pull_request.head.repo.full_name }}) ${{github.event.pull_request.base.ref}} branch.
38
+
The ${{github.event.pull_request.base.ref}} branch on nf-core repositories should always contain code from the latest release.
39
+
Because of this, PRs to ${{github.event.pull_request.base.ref}} are only allowed if they come from the [${{github.event.pull_request.head.repo.full_name }}](https://github.com/${{github.event.pull_request.head.repo.full_name }}) `dev` branch.
38
40
39
41
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.
40
42
Note that even after this, the test will continue to show as failing until you push a new commit.
0 commit comments