Release instructions, update3 + fighting unexpected merges

Author: mvanbrab

CHANGELOG.md

@@ -239,3 +239,4 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 [1.5.0]: https://github.com/SolidLabResearch/generic-data-viewer-react-admin/releases/tag/v1.5.0
 [1.6.0]: https://github.com/SolidLabResearch/generic-data-viewer-react-admin/releases/tag/v1.6.0
 [1.7.0]: https://github.com/SolidLabResearch/generic-data-viewer-react-admin/releases/tag/v1.7.0
+[Unreleased]: https://github.com/SolidLabResearch/generic-data-viewer-react-admin/compare/v1.7.0...HEAD

RELEASE.md

@@ -37,14 +37,15 @@ Squash and merge.
 
 Still in the github web interface...
 
-Create a new release, with the option to create a new git tag (our release tag, example: `v1.7.0`) on the main branch.
-
-In the release description, copy from [CHANGELOG.md](./CHANGELOG.md):
-
-* the new release section created above
-* the new release link created above
-
-Make sure to set the release as the latest release.
+Create a new release:
+
+* Choose a tag: create a new git tag (our release tag, example: `v1.7.0`).
+* Target: the main branch.
+* Release title, example: `Release v1.7.0`.
+* In the release description, copy from [CHANGELOG.md](./CHANGELOG.md):
+  * the new release section created above
+  * the new release link created above
+* Set as the latest release.
 
 ## Back on the development branch