$ Test Fixture — Blog Image Generation Workflow
Reusable, evergreen test fixture for the blog-image generation and selection workflow. Edit and push this post to trigger a real run of generate-blog-images.yml without touching any live blog post.
This post is a permanent test fixture — do not delete it. It exists so
that anyone iterating on .github/workflows/generate-blog-images.yml,
.github/workflows/pick-blog-image-by-reaction.yml, or
.github/scripts/create-image-selection-comment.ts can exercise the full
pipeline end-to-end without modifying a real published post.
How to use it
- Open a PR that touches this file in any way (e.g. bump a word in this
paragraph, or remove the
socialImageline if a previous test left it set). - The
Generate Blog Post Imagesworkflow runs because this file matchesapps/site/src/content/blog/**/*.mdxandINCLUDE_DRAFTS=trueon PRs. - Two OpenAI + two Gemini candidates are generated, the bot posts one
image-selection comment for this post, and you can pick by reacting
with the assigned emoji or by commenting
/select-image test-inline-image-preview <filename>. - After review, reset the fixture to a clean state (see below).
Resetting between runs
The generator skips posts that already have a socialImage. To reuse
this fixture for another test, remove socialImage from the frontmatter
and delete apps/site/public/media/blog-images/test-inline-image-preview.jpg
if present. The fixture is committed to the repo in that clean state.
Why a draft
draft: true keeps this out of blog listings, RSS feeds, sitemaps, and
related-post recommendations. The individual route page is technically
still generated, but isn’t reachable through normal navigation — safe
enough to keep around forever as a fixture.