| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Review⚠️ 1 warning, 💡 2 suggestions found in commit cccb4de. 👉 Fix in your agent 👈Fix the following review findings in PR #32851 (https://github.com/cloudflare/cloudflare-docs/pull/32851).
Before making changes, review each finding and present a brief summary table:
- For each finding, state whether you agree, disagree, or need clarification
- If you disagree (e.g. the fix requires disproportionate effort for minimal benefit,
or the finding is factually incorrect), explain why
- If you need clarification before deciding, ask those questions
- Then share your plan for which issues to tackle and in what order
After triaging, follow this order:
1. Post a comment on this PR for any findings you are skipping, with the finding ID and your reasoning.
2. Then commit the fixes for the legitimate findings.
The comment must come before the commit — the bot reads PR comments when a new
push triggers a review, so skip comments posted after the push will be missed.
---
## Style Guide Review
### Warnings (1)
#### SG-b2226d06741b · Use TypeScriptExample for TS/JS examples
- **File:** `src/content/docs/flagship/api-tokens.mdx` line 90
- **Issue:** Line adds a raw ` ```ts ` fenced block in a docs MDX file
- **Fix:** Replace with the `<TypeScriptExample>` component so a JS tab is auto-generated
### Suggestions (2)
#### SG-d6e56fca0a45 · Use DashButton for dashboard navigation
- **File:** `src/content/docs/flagship/api-tokens.mdx` line 34
- **Issue:** Prose links directly to `https://dash.cloudflare.com/?to=/:account/api-tokens` for navigation
- **Fix:** Use `<DashButton url="/?to=/:account/api-tokens" />` for validated dashboard deeplinks
#### SG-ec3b19329786 · Short bullet lists
- **File:** `src/content/docs/flagship/api-tokens.mdx` line 109
- **Issue:** Next steps section adds a two-item bullet list
- **Fix:** Consider rewriting the two Next steps items as prose instead of bullets
Code ReviewThis code review is in beta and may not always be helpful — use your judgment. No code review issues found. ConventionsNo convention issues found. Style Guide ReviewWarnings (1)
Only codeowners can run commands. Post a comment with the command to trigger it.
|
Sorry, something went wrong.
|
This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:
|
Sorry, something went wrong.
Sorry, something went wrong.
There was a problem hiding this comment.
see chat
Sorry, something went wrong.
🚀 Deploying Preview to Cloudflare 🚀Preview URL: https://flagship-app-scoped-tokens-cloudflare-docs.cloudflare-docs.workers.dev (commit 08f0c0e)This URL reflects your latest Preview deploymentPreview Deployments by commit
|
Sorry, something went wrong.
There was a problem hiding this comment.
🚀 🚢
Sorry, something went wrong.
Add a changelog for 2026-08-19, a how-to for creating tokens scoped to a single Flagship app, and update the client SDK warning so browsers can use Flagship App Evaluate instead of an account-wide token.
Rewrite the token page around the dashboard flow: Entire Account vs Specified Flagship apps, then pick the app and a Flagship App permission.
Add the dashboard deeplink that opens Specified Flagship apps with Flagship App Evaluate selected.
Mirror the app-scoped deeplink with a plain Account API tokens link for the account-wide flow.
Keep app-scoped tokens documented for server-side least privilege. Restore the client SDK warning and drop any guidance that puts tokens in the browser.
This release is app-scoped tokens only. Client-side evaluation is follow-up work.
* [Flagship] Document app-scoped API tokens Add a changelog for 2026-08-19, a how-to for creating tokens scoped to a single Flagship app, and update the client SDK warning so browsers can use Flagship App Evaluate instead of an account-wide token. * [Flagship] Clarify account-wide vs app-scoped tokens Rewrite the token page around the dashboard flow: Entire Account vs Specified Flagship apps, then pick the app and a Flagship App permission. * [Flagship] Link to pre-filled app-scoped token form Add the dashboard deeplink that opens Specified Flagship apps with Flagship App Evaluate selected. * [Flagship] Link account-wide token page from docs Mirror the app-scoped deeplink with a plain Account API tokens link for the account-wide flow. * [Flagship] Date changelog for 2026-08-20 * [Flagship] Stop recommending API tokens in client-side code Keep app-scoped tokens documented for server-side least privilege. Restore the client SDK warning and drop any guidance that puts tokens in the browser. * [Flagship] Date changelog for 2026-08-24 * [Flagship] Drop client-side mentions from token docs This release is app-scoped tokens only. Client-side evaluation is follow-up work.
| Back | FazBrowse Home | New Git URL |
Summary
Document Flagship app-scoped API tokens. Customers can now create a token that only evaluates or manages the Flagship apps they select, instead of every app in the account.
This PR does not change client-side evaluation guidance. A dedicated client key is follow-up work.
Documentation checklist