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/RELEASE_CHECKLIST.md
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,16 +2,17 @@
2
2
3
3
1. Check issue milestones to see outstanding issues to resolve if possible or transfer to the milestones for the next release e.g. [`v1.9`](https://github.com/nf-core/tools/issues?q=is%3Aopen+is%3Aissue+milestone%3A1.9)
4
4
2. Most importantly, pick an undeniably outstanding [name](http://www.codenamegenerator.com/) for the release where _Prefix_ = _Metal_ and _Dictionary_ = _Animal_.
5
-
3. Check whether the GitHub Actions workflow scripts need updating of the Nextflow versions
5
+
3. Check the [pipeline health page](https://nf-co.re/pipeline_health) to make sure that all repos look sane (missing `TEMPLATE` branches etc)
6
6
4. Create a PR to `dev` to bump the version in `CHANGELOG.md` and `setup.py`.
7
7
5. Make sure all CI tests are passing!
8
8
6. Create a PR from `dev` to `master`
9
9
7. Make sure all CI tests are passing again (additional tests are run on PRs to `master`)
10
10
8. Request review (2 approvals required)
11
11
9. Merge the PR into `master`
12
-
10. Wait for CI tests on the commit to passed
13
-
11. (Optional but a good idea) Run a manual sync on `nf-core/testpipeline` and check that CI is passing on the resulting PR.
14
-
12. Create a new release copying the `CHANGELOG` for that release into the description section.
12
+
10. Run `rich-codex` to regenerate docs screengrabs (actions `workflow_dispatch` button)
13
+
11. Wait for CI tests on the commit to passed
14
+
12. (Optional but a good idea) Run a manual sync on `nf-core/testpipeline` and check that CI is passing on the resulting PR.
15
+
13. Create a new release copying the `CHANGELOG` for that release into the description section.
0 commit comments