docs(lane1): report Promptly support heading item — source merged, live blocked on missing Cloudflare token - #167
Conversation
…ve blocked on missing Cloudflare token Re-verified 2026-08-15 on lane resume: fix 1536cc8 (PR #20) is in main and test-pinned; live tinystudio.in/promptly/support/ still serves the old H1->H3 outline because every deploy run fails at the fail-closed missing CLOUDFLARE_API_TOKEN step. NEEDS-NISH: provision the secret. Co-authored-by: CommandCodeBot <noreply@commandcode.ai>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
|
Warning Review limit reached
Next review available in: 14 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Free Run ID: 📒 Files selected for processing (1)
Note 🎁 Summarized by CodeRabbit FreeYour organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting https://app.coderabbit.ai/login. Comment |
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
1 participant
What
Lane 1 report for the "Restore the Promptly support heading hierarchy in production" backlog item.
Findings (re-verified 2026-08-15 ~02:45Z)
1536cc8, test-pinned inscripts/test-public-heading-hierarchy.mjs(wired intonpm test/npm run ci).https://tinystudio.in/promptly/support/still serves the old H1→H3 outline because production is a stale build..github/workflows/deploy-public-site.yml:CLOUDFLARE_API_TOKENis not set in repo secrets (onlyCLOUDFLARE_ACCOUNT_ID). Latest: run 31842883261 (pushe22785f, 2026-08-14 21:32Z).NEEDS-NISH
Provision a Cloudflare Pages:Edit token, then:
gh secret set CLOUDFLARE_API_TOKEN -R nish3451/tinystudio-inThe next main push (or workflow_dispatch) then deploys the fixed heading hierarchy with the other ~17 merged public fixes. No code change can unblock delivery.