docs: view updated extension link

[georgeciubotaru]

resolves https://github.com/holdex/wizard-browser-extension/issues/247

Summary by CodeRabbit

Release Notes

• Documentation
  • Updated the Wizard Browser Extension link in the contribution guidelines to reference the correct browser extension URL.

[coderabbitai]

Walkthrough

Updated the Wizard Browser Extension link in the documentation's TIP note, changing the reference from the GitHub Wizard extension URL to the Wizard Browser Extension URL. This is a single-line documentation edit with no functional impact.

Changes

Cohort / File(s)	Summary
Documentation Link Update docs/CONTRIBUTING.md	Updated external URL reference for the Wizard Browser Extension from GitHub Wizard link to Wizard Browser Extension link in the TIP section.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• docs: see updated name for Wizard Browser Extension #90: Updates the same documentation in docs/CONTRIBUTING.md, addressing the Wizard extension naming and references.

Suggested reviewers

• teodorus-nathaniel
• angelicawill
• williamrusdyputra

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The PR title 'docs: view updated extension link' is vague and doesn't clearly describe the main change, which is updating the extension link reference in documentation.	Use a clearer title like 'docs: update Wizard Browser Extension link' to specifically indicate which link was updated and why.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Linked Issues check	✅ Passed	The PR addresses issue #247 by updating the extension link in docs/CONTRIBUTING.md, fulfilling the checklist requirement to update the GitHub Wizard reference in that file.
Out of Scope Changes check	✅ Passed	The change is narrowly scoped to updating one extension link in documentation, directly addressing the linked issue's requirement with no unrelated modifications.
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 docstrings (stacked PR)
• 📝 Generate docstrings (commit on current branch)

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/extension-link

---

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

[georgeciubotaru]

@holdex pr submit-time 5m

[holdex]

Time Submission Status

Member	Status	Time	Action	Last Update
georgeciubotaru	✅ Submitted	5min	Update time	Mar 12, 2026, 11:39 AM
dante4rt	✅ Submitted	5min	Update time	Mar 12, 2026, 11:39 AM

---

You can submit time with the command. Example:

@holdex pr submit-time 15m

See available commands to help comply with our Guidelines.

[dante4rt]

@georgeciubotaru, just a small nitpick, I think the PR title should be user-facing

[dante4rt]

I think it's still not quite correct. As what I understand is, the title should reflect what the user gains.

If it says "update ext link", it implies that the user can update the extension, but in reality that's something we (the devs) do. Maybe something like "view updated extension link" or similar would be more accurate