Today I'm going to try to tentatively take a look at the re-organisation of deploy workflows I had been working on last month when I got blocked by a build minutes shortage. The scope has decreased somewhat in the interim because I've improved the npm module caching in the existing main website deploy workflow, so I likely no longer need to separate out the cache refresh code. The plan is to move to reusable Github Action workflows, so that all the repos, including the plugins all use the eact same build and deploy workflow which are all in a special shared repository.
This is one of those bits of work that makes you feel much better with the code base because something which is vital and often used, which currently has quite a lot of duplicated code, suddenly becomes 1 cohesive and consuatent well tested bit of code. All sorts of silly mistakes that can easily get introduced by copy paste mistakes that lead to almost the same code diverging, just totally disapear. It’s the sort ot thing that feels a bit like when you do a very thorough spring cleaning of your house, but where you've additionally built some shelves and put together some neat looking Ikea cupboards. Everything feels more robust and useful.
I’m going to ease into it, and continue with the main focus on blogging. I don’t want to get into any issues with the build minutes this month. From what I recall I had a minimum viable version working, and it was just a question of moving over the more complicated workflow into 3 seperate workflows that are each reusable. One for build, one for deploy and one for backup. Quietly optimistic and excited about it. #