Automate Zapdos website regeneration #153
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
…ush to master. Refs shannon-lab#41
cticenhour
force-pushed
the
website-automation
branch
from
1004b5e
to
330d22c
Compare
csdechant
approved these changes
Dec 7, 2022
|
@cticenhour Great work! |
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.
At long last - this PR adds a GitHub actions workflow to regenerate the Zapdos website after each push to master. An example of this workflow being run in my personal fork can be found here. If the website build fails, GitHub can also send out notifications for troubleshooting.
The total time from a merge to master to a website update should be around 30-45 minutes using this system.
Refs #41