This sets up OmniCC to use Bigwigs Packager for automated deployments to Curse and GitHub via pushing new tagged versions. Separate releases are built for both Classic and Retail. Release versions are generated by a tag in the format of 1.2.3 or v1.2.3. Beta versions are generated for tags in the format of 1.2.3-abcd or v1.2.3-abcd. Changelog information is pulled in from the changelog.md file.
Benefits:
Deploy to Curse, GitHub, and WoWInterface via the creation of a tag.
Keyword substitutions. I use this in Dominos when code needs to vary between Retail and Classic.
Drawbacks:
As before, I needed to merge both the OmniCC and OmniCC_Config folders into the main repository, so its not as easy as doing a git clone to your add-ons directory. To work around this, I clone to a central location on my computer and use a PowerShell script on Windows to test addons for retail/classic/beta/ptr
This sets up OmniCC to use Bigwigs Packager for automated deployments to Curse and GitHub via pushing new tagged versions. Separate releases are built for both Classic and Retail. Release versions are generated by a tag in the format of 1.2.3 or v1.2.3. Beta versions are generated for tags in the format of 1.2.3-abcd or v1.2.3-abcd. Changelog information is pulled in from the changelog.md file.
Benefits:
Drawbacks: