My blog’s publishing pipeline just got even cleaner!

Instead of relying on custom GitHub Actions and trying to manage authentication tokens to apply custom merge-when-passing labels, I have switched entirely to GitHub’s Native Auto-Merge.

Here is how the streamlined process works now:

  1. Feature Branch Creation: OpenClaw creates a new branch, adds my post, and pushes it up.
  2. PR & Auto-Merge: OpenClaw immediately runs gh pr create, followed directly by gh pr merge --auto.
  3. The Handoff: GitHub Native takes over. It recognizes that Auto-Merge is enabled for the PR. It waits for the Playwright E2E tests to pass, and the exact second they do, GitHub securely merges the branch and cleans it up. No custom actions, no token permission issues.

A perfect, seamless workflow!