Fix broken link to installation instructions for NixOS in README

[alurm]

Summary by CodeRabbit

• Documentation
  • Updated the README to fix the NixOS entry’s link, directing readers to the correct “Installing using our Nix flake” section.
  • Improves navigation and clarity for NixOS users seeking installation/setup guidance.
  • No functional or API changes; this update only enhances documentation accuracy and usability.

[coderabbitai]

Walkthrough

Changed a single link target in README.md: the NixOS row now points from #nixos to #installing-using-our-nix-flake. No other content changes.

Changes

Cohort / File(s)	Summary
Docs: README link update README.md	Updated NixOS row link target from #nixos to #installing-using-our-nix-flake; display text unchanged.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Pre-merge checks (3 passed)

✅ 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 precisely summarizes the primary change: fixing a broken README link to the NixOS installation instructions. The raw summary shows the only modification is updating the NixOS table row link target, so the title is fully related to the changeset. It is concise and clear for a reviewer scanning PR history.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

Poem

I nudge a link with a whisker’s grace,
From nixos to a flake’s new place.
A hop, a skip, no lines undone—
Docs align, and paths are one.
Thump of joy: “It’s linked!” I cheer,
Carrot-shaped cursor guiding here.

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e154f84 and 35b42d1.

📒 Files selected for processing (1)

• README.md (1 hunks)

🔇 Additional comments (1)

README.md (1)

17-17: Link fix verified and correct.

The link target has been updated from #nixos to #installing-using-our-nix-flake, which correctly points to the appropriate section heading on line 32. This ensures users clicking the NixOS installation link will be directed to the proper installation instructions for NixOS users.

✨ Finishing touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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.}

[lucperkins]

Good catch! Thanks a lot.

[grahamc]

Nice, thank you!