From f2a49e740fffb96e02316e1011615f08b14e8b36 Mon Sep 17 00:00:00 2001
From: Christophe '116' Loiseau <116@lab0.net>
Date: Wed, 21 Feb 2024 17:17:53 +0100
Subject: [PATCH] Code review

---
 .github/ISSUE_TEMPLATE/release.md | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/.github/ISSUE_TEMPLATE/release.md b/.github/ISSUE_TEMPLATE/release.md
index c64bebfab..9071b80d7 100644
--- a/.github/ISSUE_TEMPLATE/release.md
+++ b/.github/ISSUE_TEMPLATE/release.md
@@ -60,8 +60,7 @@ Feel free to edit this release checklist in-progress depending on what tasks nee
   - [ ] Ensure with a `docker ps -a` that all containers are healthy, and not `healthy: starting` or `healthy: unhealthy`.
 - [ ] Test the postman collection against that running docker-compose.
 - [ ] Tag the release
-  - [ ] Tag the current main with the release version in the format `vx.y.z` for instance `v1.2.3`
-  - [ ] Fetch the latest version `git fetch`, `git tag vx.y.z origin/main`, `git push origin :refs/tags/vx.y.z`
+  - [ ] In `Choose the tag`, type your new release version in the format `vx.y.z` (for instance `v1.2.3`) then click `+Create new tag vx.y.z on release`.
 - [ ] [Create a release](https://github.com/sovity/edc-extensions/releases/new) and re-use the changelog section as release description, and the version as title.
 - [ ] Check if the pipeline built the release versions in the Actions-Section (or you won't see it).
 - [ ] Revisit the changed list of tasks and compare it