Skip to content

Add scheduled launch-day auto-merge for the book announcement#1892

Open
benbalter wants to merge 1 commit into
mainfrom
launch-merge-workflow
Open

Add scheduled launch-day auto-merge for the book announcement#1892
benbalter wants to merge 1 commit into
mainfrom
launch-merge-workflow

Conversation

@benbalter

Copy link
Copy Markdown
Owner

Schedules the launch-day merge of the Open & Async announcement PR (#1891), per request to "schedule task to merge on launch day." The cloud-routine scheduler (/schedule) was unavailable, so this does it natively in GitHub Actions.

What it does

On 2026-07-21 (~10am ET) it merges #1891 — making the launch post live and flipping every site book callout to "buy now" — but only if all gates pass:

If any gate fails, it opens (or comments on) a "Launch hold" issue instead of merging. It never merges into a half-ready launch.

⚠️ Two things to do

  1. Merge this PR to main to arm it. Scheduled workflows only fire from the default branch — it can't live only on the PR it merges. (It does not merge Add launch-day post announcing Open and Async #1891 until July 21.)
  2. Recommended: add a LAUNCH_PAT repo secret (a PAT with repo scope). The deploy → email-broadcast → standard.site chain runs off the push to main, which GITHUB_TOKEN can't trigger (GitHub's recursion guard). With LAUNCH_PAT the launch behaves exactly like a human merge — including emailing subscribers. Without it, the post still deploys (the job dispatches the deploy explicitly), but the email broadcast + standard.site sync must be run manually.

Testing

Trigger manually anytime via Run workflow — defaults to a dry run (evaluates gates, merges nothing). Set dry_run: false to merge; force: true to skip the book-site check.

Validated with actionlint (clean).

🤖 Generated with Claude Code

A date-gated workflow that, on 2026-07-21, merges the Open & Async launch
PR (#1891) — making the post live and flipping the site's book callouts to
"buy now" — but only if the PR is open + mergeable, CI is green, and
open-and-async.com is actually in buy-now mode. Otherwise it opens a
"Launch hold" issue instead of merging.

Must be merged to main to arm the cron (scheduled workflows only fire from
the default branch). Uses LAUNCH_PAT if set so the merge triggers the
normal deploy → email → standard.site chain; otherwise falls back to
GITHUB_TOKEN and dispatches the deploy explicitly. Manual runs default to
a dry run for safe testing.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Updated (UTC)
✅ Deployment successful!
View logs
benbalter-github-com 31b5731 Jun 21 2026, 08:39 PM

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