From e3fe20f54b5e9aed4fb39dba199206fad1d362b1 Mon Sep 17 00:00:00 2001
From: Christoph Reiter <reiter.christoph@gmail.com>
Date: Sun, 8 Dec 2024 12:54:55 +0100
Subject: [PATCH] HACKING: add steps for creating a GH release as well

we do that since v2.20, so make sure it's written down
---
 HACKING.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/HACKING.md b/HACKING.md
index 464ab2c..9c714bd 100644
--- a/HACKING.md
+++ b/HACKING.md
@@ -18,6 +18,10 @@ git push origin +v2
 # Fetch the new changed major version tag
 cd ..
 git fetch origin --tags --force
+
+# Create a new GH release named "v2.x.x" from the release tag
+# https://github.com/msys2/setup-msys2/releases/new?tag=v2.x.x
+# Copy over the changelog entry to the GH release and set as latest release
 ```
 
 > NOTE: tag `tag-for-git-describe` is used for testing `git describe --dirty --tags` in CI. See [actions/checkout#250](https://github.com/actions/checkout/issues/250).