Skip to content

fix: updated outdated documentation links - #800

Open
ilyhalight wants to merge 2 commits into
rajnandan1:mainfrom
ilyhalight:main
Open

fix: updated outdated documentation links#800
ilyhalight wants to merge 2 commits into
rajnandan1:mainfrom
ilyhalight:main

Conversation

@ilyhalight

@ilyhalight ilyhalight commented Jul 28, 2026

Copy link
Copy Markdown

Currently they lead to 404 pages.

Also, what do you think if i try to add i18n to all /manage/* pages?

Summary by CodeRabbit

  • Documentation
    • Updated contribution guide links to the latest roadmap and versioned internationalization resources.
    • Corrected the monitor “eval” link to point to the version-specific v3 documentation.
    • Updated the user management “email service not configured” link to the current v4 email setup documentation.

@coderabbitai

coderabbitai Bot commented Jul 28, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: e88f2d2a-4614-4234-95db-72b655340efa

📥 Commits

Reviewing files that changed from the base of the PR and between af9d3c4 and 314cf05.

📒 Files selected for processing (1)
  • src/routes/(docs)/docs/content/v3/monitor-examples.md

📝 Walkthrough

Walkthrough

Updated documentation links in contributor guidance, monitor examples, and the users management page to reference revised roadmap, internationalization, v3 monitor, and v4 email setup URLs.

Changes

Documentation Link Updates

Layer / File(s) Summary
Documentation link alignment
.github/CONTRIBUTING.md, src/routes/(docs)/docs/content/v3/monitor-examples.md, src/routes/(manage)/manage/app/users/+page.svelte
Updated contributor, monitor example, and email setup links to revised or versioned documentation destinations.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Poem

A rabbit hopped through links so bright,
Making every path point right.
Roadmaps, evals, setup too,
Now versioned paths know what to do.
“Thump!” said Bun, “A tidy tune!”

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately summarizes the main change: fixing outdated documentation links.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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.

Comment thread src/routes/(docs)/docs/content/v3/monitor-examples.md Outdated
@greptile-apps

greptile-apps Bot commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

Updates outdated documentation links across three files.

  • CONTRIBUTING.md: roadmap → GitHub project; i18n → /docs/v4/internationalization
  • v3 monitor-examples: eval deep-link → /docs/v3/monitors-api#eval
  • manage users page: email-setup docs → /v4/setup/email-setup

Confidence Score: 5/5

The PR appears safe to merge; the prior eval-anchor issue is fixed and no blocking failures remain.

No blocking failure remains. The eval link now points at monitors-api#eval where the Eval heading and anchor exist.

Important Files Changed

Filename Overview
src/routes/(docs)/docs/content/v3/monitor-examples.md Eval link now targets v3/monitors-api#eval, which defines the Eval {#eval} anchor.
.github/CONTRIBUTING.md Roadmap and i18n URLs updated away from 404 paths.
src/routes/(manage)/manage/app/users/+page.svelte Email setup docs href prefixed with v4 path segment.

Reviews (2): Last reviewed commit: "Update src/routes/(docs)/docs/content/v3..." | Re-trigger Greptile

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 @.github/CONTRIBUTING.md:
- Line 48: Add exactly one trailing newline to .github/CONTRIBUTING.md after the
final content, without changing the existing contribution instructions.
🪄 Autofix (Beta)

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: ASSERTIVE

Plan: Pro Plus

Run ID: 1ed187d2-eb54-471a-91f6-745ed73d1033

📥 Commits

Reviewing files that changed from the base of the PR and between 9d99a5c and af9d3c4.

📒 Files selected for processing (3)
  • .github/CONTRIBUTING.md
  • src/routes/(docs)/docs/content/v3/monitor-examples.md
  • src/routes/(manage)/manage/app/users/+page.svelte

Comment thread .github/CONTRIBUTING.md
1. Check out the [roadmap items](https://kener.ing/docs/roadmap/)
2. Add language support by following the [i18n guide](https://kener.ing/docs/i18n/) No newline at end of file
1. Check out the [roadmap items](https://github.com/users/rajnandan1/projects/4)
2. Add language support by following the [i18n guide](https://kener.ing/docs/v4/internationalization) No newline at end of file

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Add the required trailing newline.

markdownlint reports MD047 because this file does not end with exactly one newline character.

🧰 Tools
🪛 markdownlint-cli2 (0.23.0)

[warning] 48-48: Files should end with a single newline character

(MD047, single-trailing-newline)

🤖 Prompt for 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.

In @.github/CONTRIBUTING.md at line 48, Add exactly one trailing newline to
.github/CONTRIBUTING.md after the final content, without changing the existing
contribution instructions.

Source: Linters/SAST tools

Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>
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