Repository navigation
docs(providers): update TokenLab docs links - #6474
Conversation
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
📒 Files selected for processing (1)
Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 9 remain after this review. 📝 WalkthroughWalkthroughThe TokenLab provider guide now links to ChangesTokenLab documentation links
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~3 minutes Change: Other Merge Risk: ⚪ Minimal · up to Readers can reach the intended TokenLab guides and references through the updated links. No merge-blocking issue was identified. Architecture SummaryArchitecture risk: 🔵 Low · up to The change affects 1 system. Changed systems: Architecture concerns Review detailsSystems and components
Before / after behavior
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
✅ Deterministic PR hygiene checks passed. |
✅ READY
Review readiness checklist
✅ 4/4 boxes ticked. This pull request is already Ready for Review. |
|
Link-only review at 4233cb5: I read the entire six-link diff and independently fetched all six replacement URLs without credentials. Each returns the expected TokenLab documentation title (English/Korean OpenCodex, Quickstart, Create Response, Create Message, List Models), rather than a generic homepage. This is evidence for the documentation relocation only, not renewed endorsement of provider access, pricing, or every advertised model. No inference, account action, build or security scan was performed. Required current-head CI is still a separate readiness gate; I have not marked an unrun docs build as passing. |
lidge-jun
left a comment
There was a problem hiding this comment.
Reviewed docs-site/src/content/docs/guides/providers.md at 4233cb5 (all changed lines, 605-609, 616-617 and 625).
No actionable findings. The diff contains exactly six documentation URL replacements, with surrounding Markdown, provider configuration, credential destination, model presets and referral parameters unchanged. All six new HTTPS targets returned HTTP 200 and the expected English/Korean integration, quickstart or API-reference content on 2026-10-03.
Verification: Cross-platform CI run 37077313656, attempt 2, pull_request event, head 4233cb5 succeeded, including docs site build (bun install --frozen-lockfile; bun run build), privacy gate and aggregate ci. React Doctor run 37077946385, attempt 2, on the same head succeeded. Enforce-target and hygiene passed; there are no unresolved review threads. Runtime/platform suites were correctly skipped by the docs-only scope filter and are not claimed as passing.
blocking_issues: none.
Approve for squash merge into dev.
…#6474) Replace six relocated guide and API-reference URLs with their direct destinations. Provider endpoints, routing, and configuration remain unchanged. Carries lidge-jun#6474 by @hedging8563. Co-authored-by: hedging8563 <45883076+hedging8563@users.noreply.github.com>
Summary
TokenLab documentation moved to the self-hosted
https://tokenlab.sh/docssite. The TokenLab provider guide still sends readers through the former docs subdomain. Update its six guide, quickstart and API reference links to the current direct addresses, preserving the Korean guide link and each document destination.Verification
cd docs-site,bun install --frozen-lockfile,bun run build. Built 561 pages and checked 77,818 internal links. The task container was removed after completion.devtip. No Codex/CodeRabbit findings have been raised; CodeRabbit skipped automatic review while this was a draft.Checklist
Review readiness checklist
This PR stays in draft until every box below is ticked. Tick all four boxes once the requirements are met:
Required local validation passed; commands, results, and any full-suite exception are documented.
I pushed my PR to a recent dev commit (at most 10 behind; a maintainer may still ask for the exact tip before merge).
I resolved all correct Codex and CodeRabbit findings.
My PR is ready for review.
Summary by CodeRabbit