Add build CI GitHub Actions workflow #38
Merged
Conversation
This file contains 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
|
Note: you might need to give GitHub actions write permissions to the repository in the actions tab (scroll down to "Workflow permissions". |
What's the reason for this warning? |
|
The set-output syntax is set to be deprecated sometime in the future (likely not that soon), and I tried using the newer set-output function but I was having problems with it. I'm gonna take a look into it again when I have time later today |
|
I was able to move to the new syntax to remove the warning. See #3. |
|
Alright, looks good to me!! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 PR adds a simple GitHub Actions workflow to run on push to the main branch that builds the server application for all relevant platforms using goreleaser. I'm also working on getting the workflow to run properly on pull requests, but I will PR that seperately later on. The workflow publishes the built binaries in the artifacts section. Example run: #1.