summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--CONTRIBUTING.md5
1 files changed, 5 insertions, 0 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 97532a7ed..55c5303d7 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -31,6 +31,7 @@
31 - [Javascript Coding style-checker](#javascript-coding-style-checker) 31 - [Javascript Coding style-checker](#javascript-coding-style-checker)
32 - [Packaging](#packaging) 32 - [Packaging](#packaging)
33 - [Release](#release) 33 - [Release](#release)
34 - [Nightly releases](#nightly-releases)
34 - [Updating the code after a hiatus](#updating-the-code-after-a-hiatus) 35 - [Updating the code after a hiatus](#updating-the-code-after-a-hiatus)
35 36
36<!-- /TOC --> 37<!-- /TOC -->
@@ -229,6 +230,10 @@ git push
229 230
230This will automatically trigger the build, as part of which, a new, draft release will be created [here](https://github.com/getferdi/ferdi/releases/). Once all the assets are uploaded (19 assets in total), publish the release (you will need elevated permissions in GitHub for doing this). The last commit of the `release` branch will be tagged. 231This will automatically trigger the build, as part of which, a new, draft release will be created [here](https://github.com/getferdi/ferdi/releases/). Once all the assets are uploaded (19 assets in total), publish the release (you will need elevated permissions in GitHub for doing this). The last commit of the `release` branch will be tagged.
231 232
233### Nightly releases
234
235Nightly releases are automatically triggered every day ([details](https://github.com/getferdi/ferdi/pull/990)) and available in [getferdi/ferdi](https://github.com/getferdi/ferdi/releases). Maintainers still need to verify and manually publish the draft releases as pre-releases for now.
236
232### Updating the code after a hiatus 237### Updating the code after a hiatus
233 238
234Since we are making a lot of changes that involve restructuring the code as well as taking a hard look at the dependencies (including node versions), please remember to update them by running the appropriate command of your chosen package manager. 239Since we are making a lot of changes that involve restructuring the code as well as taking a hard look at the dependencies (including node versions), please remember to update them by running the appropriate command of your chosen package manager.