Skip to content

fix: broken anchor link in ES postgresql-dump-restore tutorial#215

Closed
agustinoli wants to merge 1 commit into
developfrom
fix/broken-anchor-postgresql-dump-restore
Closed

fix: broken anchor link in ES postgresql-dump-restore tutorial#215
agustinoli wants to merge 1 commit into
developfrom
fix/broken-anchor-postgresql-dump-restore

Conversation

@agustinoli

Copy link
Copy Markdown
Contributor

Summary

  • content/tutorials/es/postgresql-dump-restore.mdx linked to #how-do-i-create-a-postgresql-database-dump on the ES postgresql-aws doc page, but that page's heading is in Spanish — the anchor never resolved.
  • Pointed the link to the actual generated slug for the Spanish heading.

Unrelated to SLEAK-5896 / SLEAK-5875 — pulled out into its own PR since it's a pre-existing issue in a different tutorial.

Test plan

  • make build — anchor no longer reported as broken

The link pointed to the English anchor slug
(#how-do-i-create-a-postgresql-database-dump) on a page whose heading
is in Spanish. Updated it to the actual generated slug.
@coderabbitai

coderabbitai Bot commented Jul 1, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@agustinoli, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 42 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: b0218c45-6550-4975-b28e-2478e5e85a62

📥 Commits

Reviewing files that changed from the base of the PR and between b377086 and 3972cfa.

📒 Files selected for processing (1)
  • content/tutorials/es/postgresql-dump-restore.mdx
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/broken-anchor-postgresql-dump-restore

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@agustinoli

Copy link
Copy Markdown
Contributor Author

Cerrado a favor de #216, que consolida los cambios de SLEAK-5896, SLEAK-5875 y el fix de anchor en un solo PR.

@agustinoli agustinoli closed this Jul 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant