Auto-merge CloudCannon publications once checks pass

[silveltman]

Temporary, for the CloudCannon setup only, until the sites move to the new CMS.

A pull request opened by cloudcannon[bot] from preview into main gets auto-merge (squash) after the Check job passes. GitHub then merges it once every required check, including CodeRabbit, is green. A failing check or an unresolved review thread keeps it open.

Auto-merge is enabled only in the 20 repositories with a CloudCannon preview site.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Preview pull requests from the automated publishing process are now set to merge into the main branch automatically after checks pass.
  • The merge uses a squash strategy and applies only to qualifying pull requests targeting the main branch. This workflow change does not add or alter any end-user-facing features.

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: 3f7ee662-ab29-4b03-8103-2284ec6f7162

📥 Commits

Reviewing files that changed from the base of the PR and between 958a193 and c47aef9.

📒 Files selected for processing (1)

• .github/workflows/check.yml

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 6 remain after this review.

---

📝 Walkthrough

Walkthrough

The workflow adds a job that runs after check. When a pull request is from cloudcannon[bot], targets main, and has head branch preview, the job uses gh pr merge to enable squash auto-merge. The job has contents: write and pull-requests: write permissions.

Priority: ➖ Normal

Estimated code review effort: 2 (Simple) | ~8 minutes

Change: Feature

Merge Risk: ⚪ Minimal · up to c47ae

This adds auto-merge for CloudCannon preview pull requests once checks pass. No actionable merge-blocking risk was found. Confirm the repository's required checks and conversation-resolution rules are configured as intended.

Architecture Summary

Architecture risk: 🔵 Low · up to c47ae

The changed surface does not map to a changed system, dependency edge, entrypoint, or external dependency.

Changed systems: None identified.

Architecture concerns
No architecture-level concerns identified.

Review details

Before / after behavior

• observed — Modified behavior in .github/workflows/check.yml: Adds a job dependent on check that enables auto-merge with squash only for pull requests from cloudcannon[bot] with head branch preview and base branch main; grants it contents and pull-request write permissions and passes the workflow token, pull-request number, and repository to the merge command.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description check	✅ Passed	The description clearly explains the temporary CloudCannon auto-merge workflow and its conditions. It matches the changeset.
Title check	✅ Passed	The title clearly and concisely summarizes the main change: automatic merging of CloudCannon publications after checks pass.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Autopilot is currently an internal CodeRabbit preview.

---

_{Comment @coderabbitai help to get the list of available commands.}