Repository Instructions
Build and Verification
Use project-local Ruby and Bundler dependencies for this GitHub Pages Jekyll site.
Run this before proposing or merging site changes:
bundle exec jekyll build
For GitHub Pages correctness, verify:
urlishttps://www.georgestarcher.combaseurlis empty for the root domain- generated CSS is available under
/assets/css/style.css robots.txtdoes not accidentally block the whole site
GitHub Actions Failure Review
When asked to check failed GitHub Actions, use gh against georgestarcher/blog.
Start with:
gh run list --repo georgestarcher/blog --status failure --limit 10
Before reading raw logs, check whether a corresponding AI Workflow Failure Summary
workflow run exists for the failed workflow. If it completed, read the GitHub
Actions run summary generated from GITHUB_STEP_SUMMARY first and use that as
the starting point for the failure report. If the summary is not available from
the CLI, include the summary workflow run URL and then inspect the raw failed
run logs.
For each relevant failed run, inspect the run and logs:
gh run view RUN_ID --repo georgestarcher/blog
gh run view RUN_ID --repo georgestarcher/blog --log
Summarize:
- workflow name and run URL
- branch, event, and commit if available
- most likely root cause
- shortest safe confirmation command
- recommended fix sequence
- whether rerun should be full workflow or a narrower job first
Do not change code while summarizing failures unless the user explicitly asks for a fix.