The build pipeline will run for every commit to main and every PR that targets main (so you can see if PR changes actually build) will artifact a Release and Debug build of the WorldsAdriftReborn, WorldsAdriftRebornGameServer and WorldsAdriftRebornServer targets (The WorldsAdriftCoreSdkDll target is included with the WorldsAdriftReborn and WorldsAdriftRebornGameServer outputs).
The release pipeline will create a bleeding-edge- prerelease for every commit to main (only for the primary repo, forks will not run this to avoid confusion). It will also try and add a changelog between it and the previous release if there is one, and it will include the files for both Release and Debug builds (structure is the same as the build artifacts).
In order to make this all possible I had to add Stripped and Publicized assemblies to the repo (which I generated using BepInEx's AssemblyPublicizer )
If you want to create a release from a prerelease, the only thing you have to do is edit the release and change the tag to something other that bleeding-edge-*.
I also updated the README to add instructions on how to install the prerelease build.
The PR is good to go as is, however comments and suggestions are always welcome :)
I suggest squashing the PR before merging, because there where a lot of testing commits ;)
TheSpookyCat
commented
1 year ago
The title says it all :)
The build pipeline will run for every commit to main and every PR that targets main (so you can see if PR changes actually build) will artifact a Release and Debug build of the WorldsAdriftReborn, WorldsAdriftRebornGameServer and WorldsAdriftRebornServer targets (The WorldsAdriftCoreSdkDll target is included with the WorldsAdriftReborn and WorldsAdriftRebornGameServer outputs).
The release pipeline will create a bleeding-edge- prerelease for every commit to main (only for the primary repo, forks will not run this to avoid confusion). It will also try and add a changelog between it and the previous release if there is one, and it will include the files for both Release and Debug builds (structure is the same as the build artifacts).
In order to make this all possible I had to add Stripped and Publicized assemblies to the repo (which I generated using BepInEx's AssemblyPublicizer )
If you want to create a release from a prerelease, the only thing you have to do is edit the release and change the tag to something other that
bleeding-edge-*.I also updated the README to add instructions on how to install the prerelease build.
The PR is good to go as is, however comments and suggestions are always welcome :) I suggest squashing the PR before merging, because there where a lot of testing commits ;)