Fix: Change Cloudflare deploy branch from main to master

[MichaelFisher1997]

Fix: Changed Cloudflare Pages deployment branch from main to master.

Problem: Deployments were showing under 'main' in Cloudflare Pages but the repository uses 'master' branch.

Solution: Updated deploy command to use --branch=master instead of --branch=main.

This is a one-line fix to ensure deployments properly associate with the master branch.

Summary by CodeRabbit

• Chores
  • Updated deployment target configuration for Cloudflare Pages deployment.

[coderabbitai]

Caution

Review failed

The pull request is closed.

📝 Walkthrough

Walkthrough

The Cloudflare Pages deployment workflow configuration was updated to change the target deployment branch from main to master in the deploy step of the GitHub Actions workflow.

Changes

Cohort / File(s)	Summary
GitHub Actions Workflow .github/workflows/build-and-deploy.yml	Updated Cloudflare Pages deployment step to deploy from master branch instead of main branch.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• ci: Add GitHub Actions workflow for Cloudflare Pages deployment #141: Modifies the same GitHub Actions workflow file with related deployment configuration changes.

Poem

🐰 A hop, a skip, from main to master dear,
The branch has changed, deployment's crystal clear!
No longer main shall lead the way,
master takes the helm today! 🚀

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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