From b320a1d28936d97e9bdd954a5f38156fc2601552 Mon Sep 17 00:00:00 2001
From: David Cook <david@redcliffs.net>
Date: Tue, 15 Aug 2023 21:38:04 +1000
Subject: [PATCH] Create release tag early for greater clarity

This way, it's clearer in the repo what is going to be released, and we don't need to copy/paste commit IDs.

([skip ci] because this branch only touches .md file)
---
 .github/ISSUE_TEMPLATE/release.md | 11 ++++++++---
 1 file changed, 8 insertions(+), 3 deletions(-)

diff --git a/.github/ISSUE_TEMPLATE/release.md b/.github/ISSUE_TEMPLATE/release.md
index 2ba7af3ba3..5a80125776 100644
--- a/.github/ISSUE_TEMPLATE/release.md
+++ b/.github/ISSUE_TEMPLATE/release.md
@@ -19,17 +19,22 @@ assignees: ''
     git commit -a -m "Update all locales with the latest Transifex translations"
     git push upstream master</pre>
   </details>
+- [ ] Create a tag:
+  <details><summary>Command line instructions:</summary>
+    <pre>
+    git tag vX.X.X
+    git push upstream vX.X.X</pre>
+  </details>  
 - [ ] [Draft new release]. Look at previous [releases] for inspiration.
-    - Select latest master commit
+    - Select new release tag
     - _Generate release notes_ and arrange into categories as required.
 - [ ] Notify [#instance-managers] of user-facing changes.
 
 ## 2. Testing
 
-- [ ] Copy the release commit below
 - [ ] Move this issue to Test Ready.
 - [ ] Notify `@testers` in [#testing].
-- [ ] Test build: [Deploy to Staging] with commit <!-- paste commit ID here, eg bb8bcecc9... -->
+- [ ] Test build: [Deploy to Staging] with release tag.
 
 ## 3. Finish on Tuesday