SCI builder#20
Merged
Merged
Conversation
Create manual-build.yml
tais
approved these changes
Nov 9, 2022
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This should kick off a build whenever a new commit is pushed to the master branch. Gamedir commits aren't detected by this, so this will have to be started manually if there's a gamedir-only change. This also means any future source + gamedir changes should be committed to gamedir first, then to source.
The version identifier is determined by the most recent commit date and hash - for example, it will appear as
Release v1.13 (Development Build) (Github) V 2022Nov09 Hash a1b2c3dNote that we shouldn't use Github as a host for this, so someone will need to upload the zip to a proper file host, unless we've got a ftp server or something.