Merge: Cloudflare deployment fixes from cursor/fix-cloudflare-deploy-main-only-9617

[unnita1235-code]

Summary

• Restrict workflow branch filters to main only (no develop / master).
• Fix failing Deploy (Cloudflare) / validate-deploy-config by changing secret validation from hard-fail to gated deploy behavior.
• If required deploy secrets are missing, workflow now emits a warning + summary and marks deploy as skipped instead of failing the push.

Root cause

deploy.yml failed immediately in validate-deploy-config when CLOUDFLARE_API_TOKEN (and related secrets) were not present in the target GitHub Environment. This blocked push checks even when deployment credentials were not configured.

Changes

.github/workflows/deploy.yml

• on.push.branches changed from [main, develop] to [main].
• Added validate-deploy-config job output can_deploy.
• Updated secret validation step to:
  • collect missing keys,
  • set can_deploy=false,
  • emit warning and job summary,
  • exit successfully (skip deploy path).
• Added if: needs.validate-deploy-config.outputs.can_deploy == 'true' to pre-deploy-checks so deploy pipeline only proceeds when secrets are available.
• Updated Pages summary text to reflect main production mapping.

.github/workflows/github-action.yml

• push branches changed from [main, master, develop] to [main].
• pull_request branches changed from [main, master, develop] to [main].

Expected outcome

• Pushes to main no longer fail in validate-deploy-config solely because deployment secrets are missing.
• Deploy jobs are cleanly skipped until secrets are configured.
• Workflow branch targeting now consistently follows main only.

  

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
aequitas-web	Ready	Preview, Comment	May 22, 2026 3:46pm
web	Ready	Preview, Comment	May 22, 2026 3:46pm