[DEV] remove git-release-test.yml

[treee111]

This PR…

• Deletes .github/workflows/git-release-test.yml.

Considerations and implementations

The workflow is a copy of git-release-pre.yml. On develop the two differ in three things only:

-name: Create pre-release with .zip files
+name: Test create release with .zip files

     branches:
-      - "release-*"
+      - git-release

+      - name: Check output
+        env:
+          RELEASE_VERSION: ${{ github.ref_name }}
+        run: |
+          echo $RELEASE_VERSION
+          echo ${{ github.ref_name }}

Everything else — checkout, copyFilesToDist.sh, the release step and its whole configuration — is identical.

Why remove it rather than keep it

A copy of the workflow it is meant to test can drift from that workflow, and this one did.

DRAFT_RELEASE: true was removed from both workflows with #178 in February 2023:

before this change, the release was a "draft release" and creating it again (by another push) was not working

Two days later it was added again — but only on the git-release branch, in one of the test / test 2 / test 3 / test 4 commits. That branch is never merged anywhere, so the flag was invisible from develop and stayed there for three and a half years.

The consequence is the bug #178 already described. UNRELEASED: update deletes and recreates the previous release by its tag, and a draft release has no tag — so the previous draft could never be found and replaced, and every run left another one behind. Four such drafts had accumulated on tag latest and have been deleted.

Testing a workflow with a copy that can silently diverge from it gives less confidence than not testing it at all.

How to test the release workflow without this file

Push a branch whose name matches release-*, for example release-test. That triggers git-release-pre.yml itself, so what is exercised is the real workflow rather than a duplicate of it.

The only thing lost is the Check output step, which echoes github.ref_name — that value is visible in the run context anyway.

Not addressed here

• git-release-pre.yml and git-release.yml both write to the latest tag. Setting UNRELEASED_TAG would let test runs use a tag of their own instead of replacing the current pre-release.
• docker://antonyurchenko/git-release:latest is unpinned. It currently resolves to v6.0.0 and has not moved since January 2024, but upstream recommends locking to a major version such as :v6.
• The git-release branch itself has no content of its own any more and can be removed. It can be recreated with git push origin develop:git-release whenever it is needed.

Pull Request Checklist

• Reviewed the Contributing Guidelines
  • Especially the Pull-Requests section
• Commits (and commit-messages) are understandable
• Tested with macOS / Linux
• Tested with Windows

🤖 Generated with Claude Code