Quantcast
WoWInterface - View Single Post - Guide: Automagically package and publish addons
View Single Post
11-16-20, 09:23 PM   #78
Niketa
A Wyrmkin Dreamwalker
 
Niketa's Avatar
AddOn Author - Click to view addons
Join Date: Jul 2013
Posts: 54
Originally Posted by StormFX View Post
Looks like most of your problem is your tags line.

For your "stable" builds, try something like:

Code:
on:
  push:
    tags:
      - '*.*.*'
      - '!*.*.*-*'
For your developmental builds, try something like:

Code:
on:
  push:
    tags:
      - '*.*.*-*'
Note the '!*.*.*-*' bit for the stable file. The ! means to ignore tags that match expression that follows, so you're explicitly telling the stable file to ignore developmental builds.

You don't need your add-on's name in tags. The packager does that and it's kind of redundant. So keep them simple, like "v2.0.4" or "v2.0.4-beta". If you must do it, make sure you include it in your tag lines for your workflows. The tag lines match the name of tags (regex-ish), so you'd do something like:

Code:
      - 'GuildBankSnapshots-*.*.*'
      - '!GuildBankSnapshots-*.*.*-*'
Etc.
This seems to have fixed the issue.

Just for educational reasons, could you explain why the previous version I had may have behaved in the way they did? Such as why it was rerunning on old tags and releasing everything as an alpha?

Also, should I have my workflows only on my stable branch or should I have it on my development branch too? I'm thinking just stable because I think it was double uploading when I had it on both, but I want to be sure I understand it right.

Thanks!
  Reply With Quote