Skip to content

ci: retire the Cloudflare Pages pull_request shadow trigger (production lane keeps push:main) - #255

Closed
Jesssullivan wants to merge 1 commit into
mainfrom
recut/pages-trigger-retirement
Closed

ci: retire the Cloudflare Pages pull_request shadow trigger (production lane keeps push:main)#255
Jesssullivan wants to merge 1 commit into
mainfrom
recut/pages-trigger-retirement

Conversation

@Jesssullivan

Copy link
Copy Markdown
Owner

Re-cut of #248 (closed in the 2026-08-12 board sweep) per operator ruling; original branch ci/retire-pages-pr-shadow@d213ed1.

Only the retirement commit is carried over. The branch's second commit (shadow-preview dispatch runner default) is intentionally excluded — it already rides on open PR #253.

…ne is production

The pull_request trigger produced build-only runs with can_deploy=false that
read as green 'shadow' checks on every PR, while real PR iteration moved to
the tailnet shadow route (shadow-preview.yml). push:main + workflow_dispatch
remain: they are the transscendsurvival.org production deploy. Filename kept
(BUILD.bazel + contract tests reference it); workflow/job names now say
production.
@Jesssullivan

Copy link
Copy Markdown
Owner Author

Closed as superseded by draft PR #251's default-owned, fail-closed workflow contraction. This recut edits the legacy Cloudflare carrier that #251 retires. The remote branch/commit remains available as a donor; do not dispatch or merge it independently.

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