docs(site): link the benchmark dashboard from the ExDoc sidebar - #27
Conversation
The benchmark page ships at /benchmarks/ but was a standalone static bundle outside the ExDoc index, so the sidebar had no link to it. - mix.exs: add a Benchmarks group (right after Operations) with a URL extra pointing at benchmarks/ (an ExDoc URLNode). The trailing slash and absence of .html keep swup from intercepting the link, which would break on a page that has no swup root. - mix.exs: centralize staging in a docs alias, docs: [docs --warnings-as-errors, ©_benchmarks/1]. It runs the strict build then copies benchmark/dashboard into doc/benchmarks via rm_rf + cp_r, so the copy is idempotent and local mix docs matches CI. The strict gate lives in the alias because Mix passes an alias CLI args only to its last command. - pages.yml: drop the now-redundant cp step and call plain mix docs.
|
Warning Review limit reached
Next review available in: 1 minute You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. 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. 📝 WalkthroughWalkthroughThe documentation build now uses a Mix alias that enables strict ExDoc warnings, stages the benchmark dashboard, and registers it under a Benchmarks section. The Pages workflow invokes this alias with a single ChangesDocumentation build
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
Suggested labels: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
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 |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@mix.exs`:
- Around line 52-55: Update the Mix alias comment to accurately state that the
alias overrides mix docs, causing Mix to forward CLI arguments to the original
docs task before the copy function runs. Remove the incorrect claim that
arguments would reach the copy function instead.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: 9443ff66-f4c6-4c92-a028-5b57750f4bf8
📒 Files selected for processing (2)
.github/workflows/pages.ymlmix.exs
The comment claimed Mix passes an alias CLI args only to the last command, so they would reach the copy function instead of docs. That is wrong for a self-named alias: in Mix.Task.run_alias, the `[^original_task | args]` clause runs the underlying docs task with `args ++ alias_args`, so any CLI args are forwarded to docs and the copy function runs afterward with none. The code is unchanged and correct: `--warnings-as-errors` is baked into the alias so a plain `mix docs` is strict everywhere (local and CI). Only the justification in the comment is fixed.
✅ PR Validation Summary
Next Steps
This comment was automatically generated by the PR validation workflow |
The benchmark page ships at /benchmarks/ but was a standalone static bundle outside the ExDoc index, so the sidebar had no link to it.
📝 Description
🔖 Type of Change
✅ Checklist
🧪 How to Test
📸 Screenshots (if applicable)
🔗 Related Issues
Note about versioning:
patch,minorormajoron the PR[major],[minor]in the titlepatch(0.0.1)Summary by CodeRabbit