docs(lane1): report Promptly privacy social share image item — source already complete in PR #26, live blocked on missing Cloudflare token - #182
Conversation
… already complete in PR #26, live blocked on missing Cloudflare token Dogfood finding 82771ab0cb63 flags /promptly/privacy's social share image as incomplete. Verified on lane resume: the full og:image block and twitter:image are already merged on main via PR #26 (commit ffe6e1f) and test-pinned (137 checks, 0 failures); live tinystudio.in/promptly/privacy/ still serves zero og:image tags 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: 59 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.
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
…ource fixed in PR #29, live blocked on missing Cloudflare token (#182) (#184) The Google AI answers disambiguation item is already fixed on main: commit 4202d54 (PR #29) put the "independent product company at tinystudio.in, not affiliated with other apps or studios using the name" statement in every public page's Organization JSON-LD, in the homepage visible copy, in llms.txt, and in its generator template, and wired scripts/test-public-brand-disambiguation.mjs into npm test and npm run ci. Re-verified against fresh origin/main: the guard script passes (11 checks, 0 failures) and the source homepage carries the identity statement. Live tinystudio.in still serves a stale bundle with no JSON-LD and no disambiguation copy, and check-public-live-deploy.mjs fails 7/15 checks; the deploy lane is fail-closed on the missing CLOUDFLARE_API_TOKEN secret (NEEDS-NISH). No source change is possible or needed; this report documents the verification. Co-authored-by: CommandCodeBot <noreply@commandcode.ai>
1 participant
Item
Outcome
No source change possible or needed. Verified against fresh origin/main
84a1563:ffe6e1f), for all 12 public pages.scripts/test-public-social-preview.mjs— 137 checks, 0 failures.tinystudio.in/promptly/privacy/serves zero og:image tags because every deploy run fails at the fail-closed missingCLOUDFLARE_API_TOKENstep (onlyCLOUDFLARE_ACCOUNT_IDis set). This is the canonical deploy-pipeline gap, outside this lane's scope.Unblock
gh secret set CLOUDFLARE_API_TOKEN -R nish3451/tinystudio-in(Cloudflare Pages:Edit token), then the next deploy carries the share-image block live.Report:
.lane/reports/fix-lane1-promptly-privacy-social-share-image-20260815.md