Update deployment workflow to be dispatchable from outside the repository #90
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
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.
Related to #78.
Updates the workflow file to be trigger-able with
repository_dispatch, so we can trigger it from the portability-articles repo when content changes.We don't actually need to do a full redeploy when portability-articles changes; we just need to repopulate the articles and regenerate index.html (
manage.py refresh) on the live instance, which is the approach I started with for this ticket. However, that was turning out to be much more work than just redeploying, and I don't see any harm in just doing a full deployment every time.