Streamline deployment #1181
Open
Streamline deployment #1181
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
A github actions workflow to automate building + deploying to gh pages
Handle building evolve.js web worker code via node.js
Remove the folders evolve/ and wiki/ generated on build
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 supersedes and is largely based on #1064 by @fredden . It's built atop #1180 .
This pull request eliminates such issues by removing the compiled files from the repository, and instead moves the compilation step to the deployment workflow.
In order to complete this work, the source for GitHub Pages should be updated from "deploy from a branch" to "GitHub Actions". It can be found here: https://github.com/pmotschmann/Evolve/settings/pages
You can find a successful deployment using this workflow at https://github.com/Argavyon/Evolve/actions/runs/10495888905
Here's how the deploy works now (this handles
npm run builditself, so no need to build locally nor push to the repo).Just go to the Actions tab, Deploy Website action, and hit the run workflow button!