This is one condition in which I might like the “If it runs, you get marks” examiners

Except for that most of it was not.
A lot of the noise on the screen (and speaker) was affected by radiation from nearby stuff.

I’d think that nowadays, it would be even more so, with way more WiFi and mobile phone signals everywhere. Now sure, different frequencies mean they would affect less, but the cumulative effect would still be more than the CMBR.

Also, I have a flat-screen CRT at home.

Guess GitHub can now claim to have created a lot more jobs.

Next, for me to check out GitLab CI.

And then keep a minimalist git serving solution for my own use.

Thanks, I’ll look into that.
While trying this time (as you can see in one of the commits), I added workflow_dispatch at the wrong place, causing a problem. Later realised that it is part of the on

I just used Google to search “zangoose github” and one of your github.io sites popped up.
That’s how I found your github.

Well, it does have triggers for other branches:

on:
  push:
    branches: [ "main" ]
  pull_request:
    branches: [ "main" ]

So, most probably would have a way to run it on other branches.

In my last workplace, I was responsible for making whatever automation I wanted (others just did everything manually) and I just appended a bunch of bash scripts to the Qt Creator Build and Run commands. It easily worked pretty well.
I guess the fancy systems are again, just to add another layer of abstraction, when everything is running on their containers instead of ours.

In those cases, I just use amend.

It’s a new website afterall, nobody is pulling that.

I’ve been meaning on spending a morning getting Nektos/ACT running.

I was just going to say I need to find a way to run it all on my system to learn it. If this can do it without actually having to push to GitHub, it would be really good for practice.