Add reference to internal benchmarks repo

[Kipok]

Summary by CodeRabbit

• Documentation
  • Enhanced documentation formatting with improved hyperlink presentation and added informational guidance notes.

[coderabbitai]

📝 Walkthrough

Walkthrough

Two documentation files were updated: a hyperlink formatting change in the basics documentation, and a new informational note directing NVIDIA employees to an internal benchmarks URL in the evaluation documentation.

Changes

Cohort / File(s)	Summary
Documentation Updates docs/basics/index.md, docs/evaluation/index.md	URL formatting converted to Markdown syntax in basics documentation; informational note added to evaluation documentation referencing an internal benchmarks resource for NVIDIA employees.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Add reference to internal benchmarks repo' directly matches the main change: adding a reference to an internal benchmarks URL in the documentation.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch igitman/add-ref-to-bench

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@docs/evaluation/index.md`:
- Around line 18-20: The docs reference an internal GitLab link in
docs/evaluation/index.md that uses a personal namespace
(https://gitlab-master.nvidia.com/igitman/nemo-skills-benchmarks), which can
break if the owner account changes; update that URL to a durable team/project
namespace (e.g., nvidia/nemo-skills-benchmarks) and similarly replace the
personal-link for nemo-skills-configs in docs/basics/index.md with the
team/project equivalent; confirm the correct org/project path with the repo
owners and update the Markdown links in both files so they point to the stable
team namespace.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Consider hosting under an org/team namespace rather than a personal one.

The URL https://gitlab-master.nvidia.com/igitman/nemo-skills-benchmarks sits in a personal GitLab namespace. If the owner leaves NVIDIA or renames their account, the link silently breaks. Hosting under a team or project namespace (e.g. nvidia/nemo-skills-benchmarks) would make the reference more durable. The same concern applies to the existing nemo-skills-configs link in docs/basics/index.md.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@docs/evaluation/index.md` around lines 18 - 20, The docs reference an
internal GitLab link in docs/evaluation/index.md that uses a personal namespace
(https://gitlab-master.nvidia.com/igitman/nemo-skills-benchmarks), which can
break if the owner account changes; update that URL to a durable team/project
namespace (e.g., nvidia/nemo-skills-benchmarks) and similarly replace the
personal-link for nemo-skills-configs in docs/basics/index.md with the
team/project equivalent; confirm the correct org/project path with the repo
owners and update the Markdown links in both files so they point to the stable
team namespace.