|
Just a thought, but in the near future, add-ons will be able to have a single package with multiple ToCs (each for a different client). You may want to consider merging your retail/classic/bc projects into one and then use the folder structure (eg, ../Skillet/Classic & ../Skillet/Retail) to separate the code, if there's too many differences between them. You could also use Lua to test the client version if the code is mostly the same, save a few lines here and there.
Additionally/Alternatively, you can use the .pkgmeta to move folders around based on the version. Eg, in the retail .pkgmeta, you could move/rename the ../Retail folder to a common name that your ToC files share and then in .pkgmeta-classic (specify in the workflow for the packager, ie, -m ".pkgmeta-classic") do the same for the ../Classic folder. This would allow you to use a single repo and workflow to produce packages for all three versions that get uploaded together.
|