⭐️ This has been superseded (for me) by Super Easy WoW Addon Releases with GitHub Actions.
The new approach is triggered by just a changelog update, handles tag creation, and bumps the TOC version for you.
Tag a commit to create a new release with zipped code and changelog-sourced notes.
You can also change the workflow configuration so it doesn't require a changelog if you really want to.
- In your GitHub repository, create a new custom workflow.
Actions > New Workflow > Set up a workflow yourself… - Name the file whatever you want.
Mine is calledAutoReleaseOnVersionTag.yml
. - Copy and paste the workflow configuration.
- Update both lines below the 🔸 comments to reflect the desired zip file name.
- Make any other adjustments, referring to the Zip Release and git-release documentation as needed.
- Commit the workflow.
- Update your changelog according to the format required by git-release.
- Commit changes locally.
- Tag the commit as
vX.Y.Z
(e.g.v3.1.1
). - Push to GitHub.
- The tag needs to be formatted as
vX.Y.Z
, but the changelog heading must be## [X.Y.Z] - YYYY-MM-DD
v1.5
will not trigger the workflow; it must bev1.5.0
.- So long as the changelog is updated, you can tag any subsequent commit to invoke the workflow.
- You probably know this if you’re a command line aficionado, but
git push
does not include tags;git push origin vX.Y.Z
does. - There’s currently no way to add tags on the GitHub website without creating a release, but there is a workaround using pre-releases.
- Obviously step #1 doesn’t matter if you’re not using a changelog.