Skip API deploy step when Cloudflare secrets are missing

[Copilot]

The deploy GitHub Actions job failed because wrangler deploy was executed without required Cloudflare credentials in CI. This change makes deploy execution conditional on secret availability so the workflow does not hard-fail when secrets are unset.

• Workflow guard for deploy credentials

  • Added an if condition to run npm run deploy -w @protectedshare/api only when both CLOUDFLARE_API_TOKEN and CLOUDFLARE_ACCOUNT_ID are present.

• Explicit skip path

  • Added a companion step that runs when either secret is missing and emits a clear skip message, making the behavior intentional and visible in workflow logs.

- name: Deploy Cloudflare Worker
  if: ${{ secrets.CLOUDFLARE_API_TOKEN != '' && secrets.CLOUDFLARE_ACCOUNT_ID != '' }}
  run: npm run deploy -w @protectedshare/api

- name: Skip deploy when Cloudflare secrets are missing
  if: ${{ secrets.CLOUDFLARE_API_TOKEN == '' || secrets.CLOUDFLARE_ACCOUNT_ID == '' }}
  run: echo "Skipping deploy because CLOUDFLARE_API_TOKEN and/or CLOUDFLARE_ACCOUNT_ID is not configured."

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
protectedshare-api	Ready	Preview, Comment	Jun 10, 2026 11:14am
protectedshare-web	Ready	Preview, Comment	Jun 10, 2026 11:14am