I’ve captured the inputs and output of the workflow below. The process basically involved adding a new local remote named dev to my existing rootstalk-DO local repository, and doing a git fetch of that new remote. Everything in the code block that follows is as-it-was-executed on my Grinnell College MacBook…
I got the following email from Azure indicating a failed deployment. Why? Well, because a GitHub Action from the rootstalk remote, one that’s intended only to run in that repository’s Azure environment, got executed here in the new rootstalk-DO repository. Fortunately, this does NO HARM.
[Digital-Grinnell/rootstalk-DO] Run failed: Azure Static Web Apps CI/CD - main (7a1c223)
Perhaps I need to investigate a way to populate that config.toml variable at compile-time? That would be sweet!
The Good News
The good news is simple… IT WORKED! Rootstalk is now up-to-date, with the minor issue reported above, and the deployment to DigitalOcean was automatic, as intended. The message I see in my DigitalOcean dashboard says:
Dec 22 2021
Digital-Grinnell's deployment went live
Trigger: Digital-Grinnell pushed 7a1c223 to Digital-Grinnell/rootstalk-DO/main
And that’s a wrap. Until next time, stay safe and wash your hands! 😄