fix(public): repair homepage managed-service heading hierarchy (H2->H3) - #51
Conversation
The managed-service section on the homepage placed an H4 directly under the section's H2, skipping H3 in the document outline. Change the feature heading to a semantic H3 and keep its former h4 scale and margin via .team-feature :is(h3, h4) plus .team-feature h3, so the block renders identically.
The homepage was missing from the heading-hierarchy coverage, which is why the managed-service H2 -> H4 skip went unnoticed. The check now asserts the homepage outline is jump-free, the managed-service section starts H2 then H3, and the CSS pairing keeps the former h4 scale and margin.
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
There was a problem hiding this comment.
nish3451 has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.
|
Warning Review limit reached
Next review available in: 37 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: Pro Plus Run ID: 📒 Files selected for processing (3)
Comment |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
There was a problem hiding this comment.
nish3451 has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.
The fleet keeps dispatching the same finding to multiple lanes, producing duplicate same-fix PR pairs: #36/#44 and #55/#56 are byte-identical or near-identical patches of the operator export --help fix, #39/#49 the offername article fix, #40/#52 the recording exporter --help fix, plus #38/#48/#51, #30/#61/#72, #45/#64, #42/#60, #43/#54 and #46/#74. Add a PR Duplicate Guard: - scripts/check-pr-duplicates.mjs compares a PR's diff against every other open PR (shared changed-file coverage >= 0.8 and patch similarity >= 0.5). Calibrated on all 79 open PRs on 2026-08-11: every pair above the thresholds was a genuine duplicate-cluster member, zero false positives. - .github/workflows/pr-duplicate-guard.yml runs it on every PR event and posts one marker comment naming the duplicate(s) and the canonical PR; the check fails loudly when a duplicate is found. Informational, not required. - scripts/test-pr-duplicates.mjs covers parsing, similarity, detection, and comment upsert with an injected API; wired into npm ci and npm test.
There was a problem hiding this comment.
nish3451 has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.
There was a problem hiding this comment.
nish3451 has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
1 participant
Canonical landing of the homepage managed-service heading fix. Resolves the unreviewed-by-grok finding that two open PRs (#38, #48) implemented the same fix: the homepage managed-service section skipped H2 -> H4 and was missing from the public heading-hierarchy check. PR #38 is already closed unmerged; PR #48 is closed as superseded by this one, so the fix lands exactly once.
Fix
public/index.html: the managed-service feature heading is now a semantic H3 directly under the H2 section title (was H4), so the outline reads H1 -> H2 -> H3 with no jumps.public/styles.css: the H3 keeps the former h4 scale and margin inside.team-feature(.team-feature :is(h3, h4)pairing +.team-feature h3scale), so the feature block renders identically to before — no visible change.Coverage
scripts/test-public-heading-hierarchy.mjsnow coverspublic/index.html: homepage outline must be jump-free, the#managed-servicesection must start H2 then H3, and the CSS pairing must keep the former scale. Negative-verified against the pre-fix homepage (flags the H2 -> H4 jump).Verify
node scripts/test-public-heading-hierarchy.mjs: 52 checks, 0 failuresgit diff --checkclean