From b9da06c7eb6c201da8251bf8f281bd686fdde047 Mon Sep 17 00:00:00 2001
From: Andrew Olsen <andrew.olsen@koordinates.com>
Date: Thu, 9 Feb 2023 15:00:06 +1300
Subject: [PATCH] Update HOW-TO-RELEASE.md - push commit + tag

---
 HOWTO-RELEASE.md | 9 +++++++--
 1 file changed, 7 insertions(+), 2 deletions(-)

diff --git a/HOWTO-RELEASE.md b/HOWTO-RELEASE.md
index a2719007b..28660f4c5 100644
--- a/HOWTO-RELEASE.md
+++ b/HOWTO-RELEASE.md
@@ -24,9 +24,14 @@ This process only supports a single release branch (master). It'll need to be ex
 
 8. Update `CHANGELOG.md` to refer to the new version (ie, make sure it doesn't say "UNRELEASED" next to all the latest changes.)
 
-9. Commit with a message like "Release v1.2.3"
+9. Commit with a message like "Release v1.2.3", and push the commit.
 
-10. Tag the release with the Git tag version format and push it:
+    ```console
+    $ git commit -m "Release v1.2.3"
+    $ git push
+    ```
+
+10. Tag the release with the Git tag version format and push the tag.
 
     ```console
     $ git tag v1.2.3