Skip to content

Staging branch: CI on pushes, flow in the README - #16

Merged
farhanmasud merged 1 commit into
stagingfrom
chore/staging-branch
Nov 6, 2026
Merged

farhanmasud merged 1 commit into
stagingfrom
chore/staging-branch

Conversation

@farhanmasud

Copy link
Copy Markdown
Member

The first PR into staging.

  • CI runs on pushes to staging as well as main. It already ran on every PR.
  • README → Development says PRs go to staging (preview at https://staging.image-optimizer-7ba.pages.dev), and staging is merged into main (the live site).

Already set up on GitHub (not part of this diff)

  • staging was created from main (cfc439a).
  • "Automatically delete head branches" is on, so feature branches go away when their PR merges.
  • Ruleset "Keep main and staging": neither branch can be deleted or force-pushed. Without it, auto-delete would delete staging the first time it's merged into main.

When merging staging into main

Use Create a merge commit, not Squash or Rebase. Squashing gives main new commits that staging doesn't have, and the next release PR then conflicts with itself.

🤖 Generated with Claude Code

https://claude.ai/code/session_01STHRjFYWhkJBxSKG3tJdap

@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying image-optimizer with  Cloudflare Pages  Cloudflare Pages

Latest commit: 12519b4
Status: ✅  Deploy successful!
Preview URL: https://4cf693e5.image-optimizer-7ba.pages.dev
Branch Preview URL: https://chore-staging-branch.image-optimizer-7ba.pages.dev

View logs

@farhanmasud
farhanmasud merged commit dc2bd32 into staging Nov 6, 2026
2 checks passed
@farhanmasud
farhanmasud deleted the chore/staging-branch branch November 6, 2026 14:47
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