AI Workflow ยท Portfolio

Turning a Legacy Jekyll Posting Mistake into Canonical Source Guardrails

How a post pushed to the old GitHubPageMaker repository failed to appear on the live Astro site, and how the workflow was guarded against repeating it.

May 31, 2026

Root Cause

The post was committed and pushed successfully, but it was written to the legacy Jekyll repository. The live site is now built from the Astro repository and deployed through GitHub Actions to Cloudflare Pages.

Fix

  • Moved the post into the Astro content collection with the correct frontmatter.
  • Updated localized post summaries and locale validation for the new slug.
  • Removed the mistaken Jekyll post from the legacy repository.
  • Added a deprecated-source notice and pre-commit guard to the old repository so new `_posts` edits are blocked by default.

Rule

A successful push is not a deployment proof after a migration. Future agents must verify the canonical source repository, run build and validation, then check the Cloudflare Pages URL and tag listing.