Thank you for this guide!
I already had a .pkgmeta for the CurseForge packer so setting this up for my addon was quite easy and I got my first automated release to WoWI
I am a bit confused about the release to GitHub. I used the "Draft a Release" feature on the side but that does not work with the packer since that already creates a release on the site?
Code:
Uploading ChocolateBar-v3.1.2.zip (7.3.0) to https://www.wowinterface.com/downloads/info12326
Success!
Creating GitHub release: https://github.com/zanony/ChocolateBar/releases/tag/v3.1.2
Error! (422)
{
"message": "Validation Failed",
"errors": [
{
"resource": "Release",
"code": "already_exists",
"field": "tag_name"
}
],
"documentation_url": "https://developer.github.com/v3/repos/releases/#create-a-release"
}
After trying with
Code:
git tag v3.1.3 && push --tags
the packer did release to GitHub but took the wrong tag (the one before the current).
Two side notes:
As you mentioned I had to adjust the regular expression in the .travis.yml to work with my version scheme. It has a leading "v". Since this version scheme is quite common you could include an info how to adjust regex for that scheme in the guide.
I noticed that the CurseForge link to the
keywords substitutions has changed.