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
Many thanks for taking an interest in improving nf-core/rnadeseq.
4
+
Many thanks for taking an interest in improving qbic-pipelines/rnadeseq.
5
5
6
-
We try to manage the required tasks for nf-core/rnadeseq using GitHub issues, you probably came to this page when creating one.
6
+
We try to manage the required tasks for qbic-pipelines/rnadeseq using GitHub issues, you probably came to this page when creating one.
7
7
Please use the pre-filled template to save time.
8
8
9
9
However, don't be put off by this template - other more general issues and suggestions are welcome!
@@ -13,8 +13,8 @@ Contributions to the code are even more welcome ;)
13
13
14
14
If you'd like to write some code for qbic-pipelines/rnadeseq, the standard workflow is as follows:
15
15
16
-
1. Check that there isn't already an issue about your idea in the [nf-core/rnadeseq issues](https://github.com/nf-core/rnadeseq/issues) to avoid duplicating work. If there isn't one already, please create one so that others know you're working on this
17
-
2.[Fork](https://help.github.com/en/github/getting-started-with-github/fork-a-repo) the [nf-core/rnadeseq repository](https://github.com/nf-core/rnadeseq) to your GitHub account
16
+
1. Check that there isn't already an issue about your idea in the [qbic-pipelines/rnadeseq issues](https://github.com/qbic-pipelines/rnadeseq/issues) to avoid duplicating work. If there isn't one already, please create one so that others know you're working on this
17
+
2.[Fork](https://help.github.com/en/github/getting-started-with-github/fork-a-repo) the [qbic-pipelines/rnadeseq repository](https://github.com/qbic-pipelines/rnadeseq) to your GitHub account
18
18
3. Make the necessary changes / additions within your forked repository following [Pipeline conventions](#pipeline-contribution-conventions)
19
19
4. Use `nf-core schema build` and add any new parameters to the pipeline JSON schema (requires [nf-core tools](https://github.com/nf-core/tools) >= 1.10).
20
20
5. Submit a Pull Request against the `dev` branch and wait for the code to be reviewed and merged
@@ -99,3 +99,18 @@ If you are using a new feature from core Nextflow, you may bump the minimum requ
99
99
### Images and figures
100
100
101
101
For overview images and other documents we follow the nf-core [style guidelines and examples](https://nf-co.re/developers/design_guidelines).
102
+
103
+
## GitHub Codespaces
104
+
105
+
This repo includes a devcontainer configuration which will create a GitHub Codespaces for Nextflow development! This is an online developer environment that runs in your browser, complete with VSCode and a terminal.
106
+
107
+
To get started:
108
+
109
+
- Open the repo in [Codespaces](https://github.com/qbic-pipelines/rnadeseq/codespaces)
Copy file name to clipboardExpand all lines: .github/PULL_REQUEST_TEMPLATE.md
+1-2
Original file line number
Diff line number
Diff line change
@@ -15,8 +15,7 @@ Learn more about contributing: [CONTRIBUTING.md](https://github.com/qbic-pipelin
15
15
16
16
-[ ] This comment contains a description of changes (with reason).
17
17
-[ ] If you've fixed a bug or added code that should be tested, add tests!
18
-
-[ ] If you've added a new tool - have you followed the pipeline conventions in the [contribution docs](https://github.com/nf-core/rnadeseq/tree/master/.github/CONTRIBUTING.md)
19
-
-[ ] If necessary, also make a PR on the nf-core/rnadeseq _branch_ on the [nf-core/test-datasets](https://github.com/nf-core/test-datasets) repository.
18
+
-[ ] If you've added a new tool - have you followed the pipeline conventions in the [contribution docs](https://github.com/qbic-pipelines/rnadeseq/tree/master/.github/CONTRIBUTING.md)
20
19
-[ ] Make sure your code lints (`nf-core lint`).
21
20
-[ ] Ensure the test suite passes (`nextflow run . -profile test,docker --outdir <OUTDIR>`).
22
21
-[ ] Usage Documentation in `docs/usage.md` is updated.
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
+
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."
17
+
close-issue-message: "This issue was closed because it has been tagged as awaiting-changes or awaiting-feedback by an nf-core contributor and then staled for 20 days with no activity."
0 commit comments