3 posts tagged with "GitHub"

Reviewing What Went Wrong​

After my first adventures with GitHub spec-kit, I was left pretty disappointed with the results. The structure and architecture looked fine on the surface, but the actual implementation was mostly placeholders. Tasks were marked as complete when they clearly weren’t, and authentication that was supposed to use Azure AD and Google was just accepting any username and password. Not good enough.

Since starting this experiment, I’ve switched to Claude Sonnet 4.5, which is a big step up from the previous model. With better prompts and a more capable LLM, I wanted to dig into why things went wrong the first time—and, more importantly, how to avoid those mistakes in future.

A Most Agreeable Distraction​

I dare say, dear reader, that after several weeks regaling you with tales of aortic replacements and pacemaker adventures, you might be rather relieved to encounter a proper technical post. Whilst convalescing in Kirchberg Hospital, waiting for my INR levels to reach their proper therapeutic range, I find myself with time on my hands and only my trusty phone and a modest tablet for company.

What better opportunity, I thought, to explore GitHub's spec-kit and attempt some spec-driven development? The goal, rather splendidly practical given my current circumstances, is to build an application to remind me to take my blood-thinning medication in the evening and perform my INR blood tests in the morning. I've imaginatively titled this endeavour the blood_thinner_INR_tracker.

based on these gists https:/gist.github.comjpiersonb6c0815e9dd7078f6b8cc3cb9076ddf4 https:/gist.github.comElectricRCAircraftGuy8ca9c04924ac11a50d48c2061d28b090 fork the repository in github go to team explorer repository settings  rename local origin to upstream (and update push address to the new repo, or you will always have items waiting to be pushed)  add new remote called origin  commit any changes fetch from new origin - won't work if there are conflicting changes, pull and merge worked update push remote to use origin rather than upstream, otherwise you will still be pushing to the original repo which you likely don't have permissions on and will see something like

Error encountered while pushing to the remote repository: Git failed with a fatal error.
unable to access 'https:/github.com...Demo.AspNetCore.PushNotifications.git': The requested URL returned error: 403
Pushing to https:/github.com...Demo.AspNetCore.PushNotifications.git