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.
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.