Skip to content

ci: remove banned Jekyll workflow (per estate language policy)#31

Merged
hyperpolymath merged 1 commit into
mainfrom
ci/remove-banned-jekyll-workflow
May 30, 2026
Merged

ci: remove banned Jekyll workflow (per estate language policy)#31
hyperpolymath merged 1 commit into
mainfrom
ci/remove-banned-jekyll-workflow

Conversation

@hyperpolymath
Copy link
Copy Markdown
Owner

Summary

jekyll-gh-pages.yml is a banned-language workflow per the 2026-05-25 estate language policy ([[feedback_no_jekyll_use_casket_ssg]]). It fails on every push and red-mains this repo.

Fix

Delete the workflow file. For Pages publishing, use casket-pages.yml (canonical casket-ssg-based template in hyperpolymath/standards). Tracked under hyperpolymath/standards#306.

Estate-wide context

One of 12 repos affected. Caught by the 2026-05-30 estate CI/CD audit.

🤖 Generated with Claude Code

Jekyll is banned estate-wide per [[feedback_no_jekyll_use_casket_ssg]]
(banned 2026-05-25). `.github/workflows/jekyll-gh-pages.yml` was
failing on every push (Pages not enabled + banned-language policy red)
and contributing to red main on this repo.

For repos that genuinely need GitHub Pages publishing, use the canonical
casket-ssg-based workflow (`casket-pages.yml` from hyperpolymath/standards).
Tracked under hyperpolymath/standards#306.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@hyperpolymath hyperpolymath enabled auto-merge (squash) May 30, 2026 17:04
@hyperpolymath hyperpolymath merged commit 4a94ff0 into main May 30, 2026
10 of 20 checks passed
@hyperpolymath hyperpolymath deleted the ci/remove-banned-jekyll-workflow branch May 30, 2026 17:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant