Since my last post I’ve mostly gone back to working on The Stack.

It’s reached that fiddly phase where the basic MVP functionality is probably in, but there are lots of little features and tweaks that are vying for inclusion.

Meanwhile the UI is a bit clunky and definitely needs some work, but how much is enough for now? Perfect is the enemy of good and all that…

Whilst working on ActionBuilderTool, I was getting an annoying test failure.

A couple of my tests generate a workflow, and compare it against the expected text, which is 50+ lines of text.

Unfortunately the basic #expect(generatedYAML == expectedYAML) implementation doesn’t do a very good job of explaining where the mismatch is…

In my last post about automating Github actions workflow generation, I said I’d revived the old tool I wrote a while back, and got it working again (for some value of “working”).

I already figured that there was more to do, and then the post got an unexpected mention in iOS Dev weekly (thanks Dave!).

Once I’d got over my initial shock that anyone was paying attention (!), I decided that I definitely ought to spend a bit more time in the code… so that’s what I’ve been doing today.

I’ve been using Copilot for a couple of years, but mostly limited it to grunt work; auto-completing obvious code, filling out obvious patterns, and drafting comments (some of which I accept).

Recently I’ve been looking for an excuse to try out something more ambitious. More vibe-codey. Whatever the fuck that means.

Then it hit me. I built this website a few years ago with Jekyll and Bootstrap, which frankly are things I know little about. The world has moved on, but the website hasn’t.

This seemed like a perfect test case…

Today I’ve been looking at reviving a tool that I built a while ago, which automatically builds a Github Actions workflow file for a Swift package.