Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: sync dev with main #50

Merged
merged 4 commits into from
Aug 23, 2023
Merged

chore: sync dev with main #50

merged 4 commits into from
Aug 23, 2023

Conversation

alandtse
Copy link
Collaborator

Just noted we had some older PRs that didn't make it to dev yet.

alandtse and others added 4 commits August 21, 2023 12:39
This should help automate building test releases for both branches
and the mainline. It takes a lot longer than building on a typical
programmer PC with fast disks and warm caches, but it will generate
reproducible builds and maybe reduce some of the by-hand work CS
contributors are doing.

The workflow generates a mod structure identical to the one the bat
files generates, then compresses the result into a 7zip archive.
The archive is then uploaded as an asset to a draft GitHub release
named for the tag. To publish the release on GitHub, a human must
edit the release notes and press the publish button.

This workflow caches the cmake `build` directory. The vcpkg
action caches the vcpkg binary artifacts. Most of the build time
is currently spent rebuilding CommonLibSSE-NG because it's
pulled in as a git submodule. Figuring out how to cache that
build artifact on its own would speed this up a lot. (Maybe pulling
it in as a vcpkg release instead? But that decision is above my
pay grade.)
A workflow for building releases on tag push
@doodlum doodlum merged commit 838fc57 into dev Aug 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants