Inspect Cloudflare staging access without resource changes - #8
Merged
OneClickPostFactory merged 2 commits intoSep 9, 2026
Merged
Conversation
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
oneclickpostfactory-agent | 45f2013 | Commit Preview URL Branch Preview URL |
Sep 08 2026, 01:44 PM |
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
1 participant
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.
Adds a bounded read-only Cloudflare account diagnostic using the existing upstream Actions credentials. Two fixed GET endpoints inspect Workers and Container applications. No checkout, dependency install, secret export, resource mutation, deployment or live publication occurs. Logs contain counts, numeric error codes and only matching OneClick/staging resource names; unrelated application names and raw responses are omitted. The branch-only push trigger runs the initial inspection, and manual dispatch supports later checks. Production rollout remains gated on schema-first staging, legacy revision reconciliation and the existing exact-SHA deployment approval.