Modify GitHub Actions workflows to trigger workflows in the site starter repository

[jaylenw]

Problem

Originally, with Circle-CI, there was a scheduled workflow that had the site starter rebuilt nightly. This was done because sometimes when the data is updated on the data repository, the site would not show the new data. After the nightly build was done, it will deploy the same code base of the site but now with the updated data. We want to have a GitHub Actions workflow that triggers the rebuild and deployment of the the site for the environment that was updated in the data starter repository with new data.

Solution

Look into implementing a way with GitHub Actions in having a workflow trigger another workflow. When the development branch of this repository is updated, it will run the workflow to build and deploy the data to CloudFront, at the end of the workflow it should trigger the workflow to build and deploy the site from the development branch. Implement the same for production.

[hunterowens]

You can just add an `on: schedule (nightly cron)` to the nightly workflow along with pushes to productions in the `workflow.yml`

…

On Mon, Mar 15, 2021 at 10:05 AM Jaylen Wimbish ***@***.***> wrote: Problem Originally, with Circle-CI, there was a scheduled workflow that had the site starter rebuilt nightly. This was done because sometimes when the data is updated on the data repository, the site would not show the new data. After the nightly build was done, it will deploy the same code base of the site but now with the updated data. We want to have a GitHub Actions workflow that triggers the rebuild and deployment of the the site for the environment that was updated in the data starter repository with new data. Solution Look into implementing a way with GitHub Actions in having a workflow trigger another workflow. When the development branch of this repository is updated, it will run the workflow to build and deploy the data to CloudFront, at the end of the workflow it should trigger the workflow to build and deploy the site from the development branch. Implement the same for production. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#12>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AANHXYVZRHURHMFSZWV6PDDTDY44JANCNFSM4ZG6G5HQ> .

[jaylenw]

Hey @hunterowens , thanks for your input. We were thinking about that and will implement it if we are unable to add a trigger. We are thinking that the site owners would like to see their updated content made to the data repository reflect on the site soon after the changes were made. By having the trigger, they will not have to wait until the morning or trigger a manual rebuild of the site to see the latest data changes.

[tmargono]

Need to modify event_type to differentiate between dev and prod workflow runs. https://docs.github.com/en/actions/reference/events-that-trigger-workflows#repository_dispatch