add explicit build and deploy gh actions #4
Merged
Conversation
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
- Explicit actions allows for pinning dependencies for consistent builds. Signed-off-by: Derek Worthen <[email protected]>
dworthen
force-pushed
the
jekyll-build
branch
from
c574799 to
3aad0ec
Compare
emrekiciman
approved these changes
Sep 16, 2022
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.
There was an issue with the last deployment in which most pages were missing content. It turns out that the implicit build action GitHub uses for building and deploying Jekyll sites is still on Jekyll 3.x instead of 4.x. I added explicit GitHub actions for building and deploying so we can pin dependency versions for consistent builds.
On pull requests to main the action will build the site and on merge/pushes to main the action will build and deploy the site.