You push your changes to GitHub, including a tag which signifies a new release/version. These tools combined will automatically do everything you would normally do when publishingĪ new version for your addon(s), such as increasing the Version field in your TOC file,įetching localization, embedding libraries and more, then finally zip everything and publish.Īfter the setup (see the next two posts), the following happens: Last but not least there is the BigWigs packager script which will do all of the actual work for us. We'll be using this to package and release our addon(s). If you've heard of (or used) Git, you've probably also heard of (and used) GitHub,Īn online service that lets you host your Git repositories in the cloud.īut you've probably not heard of Travis CI, it's a tool exclusively made for GitHub that lets developers runĪutomated tests on their code. You've probably already heard of Git, it's basically a tool to keep track of changes done to 
To do this we're going to rely on a few tools. With this tool, addons can be published at the two major addon sites CurseForge/WoWAce (and thus Curse), and WoWInterface.Īddons can also be published (packaged) on GitHub in case you'd also want that. So you can focus more on developing the addon itself. This guide will instruct you how you can automate packaging and publishing new releases, The rest of this guide is still valid, but if you want to use GitHub actions instead of TravisCI please see this: Īny seasoned developer will agree that automating repetitive tasks is a good idea,Īnd one of the most repetitive things we do as addon developers is publishing addon updates. The TravisCI section of this guide is no longer maintained, as the majority of the community has moved over to use GitHub Actions instead.
0 kommentar(er)
