Skip to content

Skip Cloudflare deploy step when secrets are not configured#1737

Draft
Copilot wants to merge 2 commits intomainfrom
copilot/fix-github-actions-workflow-again
Draft

Skip Cloudflare deploy step when secrets are not configured#1737
Copilot wants to merge 2 commits intomainfrom
copilot/fix-github-actions-workflow-again

Conversation

Copy link
Copy Markdown
Contributor

Copilot AI commented Mar 22, 2026

The build-and-deploy workflow was unconditionally running the Cloudflare Pages deploy step, causing it to fail when CLOUDFLARE_API_TOKEN and CLOUDFLARE_ACCOUNT_ID are not yet configured in the repository.

  • Guard deploy step: Added an if condition so the deploy step is skipped rather than failing when either Cloudflare secret is absent
- name: Deploy to Cloudflare Pages
  if: ${{ secrets.CLOUDFLARE_API_TOKEN != '' && secrets.CLOUDFLARE_ACCOUNT_ID != '' }}
  uses: cloudflare/wrangler-action@v3
Original prompt

Fix the failing GitHub Actions workflow build-and-deploy
Analyze the workflow logs, identify the root cause of the failure, and implement a fix.
Job ID: 68079691244
Job URL: https://github.com/benbalter/benbalter.github.com/actions/runs/23403977468/job/68079691244


📍 Connect Copilot coding agent with Jira, Azure Boards or Linear to delegate work to Copilot in one click without leaving your project management tool.

Copilot AI changed the title [WIP] Fix failing GitHub Actions workflow build-and-deploy Skip Cloudflare deploy step when secrets are not configured Mar 22, 2026
Copilot AI requested a review from benbalter March 22, 2026 13:51
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.

2 participants