This site works best with JavaScript enabled. Please enable JavaScript to get the best experience from this site.
Our first step of the new Authors Portal is Live! Learn more or click here to check it out!
storm- can you point to your addon being built by curseforge on a branch? (maybe they fixed it since I tried it a couple of weeks back)
https://www.wowace.com/projects/masque
I do global/general updates on /master, then switch to /classic, do a merge: master > classic, make any changes I need to do on /classic, tag /classic, switch to master, tag /master and push all.
I switched to github actions to build and push both classic and bfa versions automatically:
eg
https://github.com/mooreatv/NeatMinimap/blob/master/.github/workflows/packaging.yaml
storm- can you point to your addon being built by curseforge on a branch? (maybe they fixed it since I tried it a couple of weeks back)
https://www.wowace.com/projects/masque
I do global/general updates on /master, then switch to /classic, do a merge: master > classic, make any changes I need to do on /classic, tag /classic, switch to master, tag /master and push all.
I switched to github actions to build and push both classic and bfa versions automatically:
eg
https://github.com/mooreatv/NeatMinimap/blob/master/.github/workflows/packaging.yaml