Verify GitHub Cloudflare auto-deploy credentials - #24
Merged
Merged
Conversation
Empty commit to run Deploy Cloudflare Worker on main with the replaced Actions secrets. Co-authored-by: Myles Cook <MylesMCook@users.noreply.github.com>
MylesMCook
marked this pull request as ready for review
September 14, 2026 21:01
There was a problem hiding this comment.
Copilot wasn't able to review any files in this pull request.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed?
Empty commit so
Deploy Cloudflare Workerruns onmainafter the Cloudflare Actions secrets were replaced.How did you check it?
This PR exists to trigger the production deploy job. The check is a green
Deploy Cloudflare Workerrun on the merge commit, then live/and/api/parseon both workers.Anything that could break?
If the new token is still invalid or under-scoped, the deploy job fails at Wrangler the same way as runs
34890315478and34888752288. No app code changes.