chore: restored the broken CodeRabbit badge and added a link to it

[Olexandr88]

Description of the changes

Summary by CodeRabbit

• Documentation
  • Updated the CodeRabbit PR Reviews badge to a new static design in project documentation.

[coderabbitai]

Walkthrough

The README.md file has been updated to replace a dynamic CodeRabbit PR-count badge with a static badge labeled "CodeRabbit-PR Reviews" that links to coderabbit.ai, changing the badge source URL and destination link.

Changes

Cohort / File(s)	Change Summary
Badge Update README.md	Replaced dynamic CodeRabbit PR count badge (shields.io with dynamic stats) with static "CodeRabbit-PR Reviews" badge; updated link destination to coderabbit.ai

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

• Single cosmetic documentation change with no functional impact
• Badge URL and link replacement only

Possibly related PRs

• chore: add CodeRabbit Pull Request Reviews Badge #1543: Directly modifies the same CodeRabbit PR Reviews badge in README.md with related badge replacement logic.

Suggested reviewers

• alexandre-abrioux
• kevindavee
• rodrigopavezi
• sstefdev

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description only contains the template header without any actual content describing the changes, failing to provide substance beyond the boilerplate.	Add a detailed description explaining why the CodeRabbit badge was broken, what was changed, and why the new link is beneficial.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: restoring a broken CodeRabbit badge and adding a link to it, which matches the README.md modifications shown in the summary.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

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

---

📜 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 734baa2 and 71d542c.

📒 Files selected for processing (1)

• README.md (1 hunks)

🧰 Additional context used

🧠 Learnings (2)

📚 Learning: 2025-01-20T12:54:19.675Z

Learnt from: rodrigopavezi
Repo: RequestNetwork/requestNetwork PR: 1547
File: packages/request-client.js/src/http-data-access.ts:114-114
Timestamp: 2025-01-20T12:54:19.675Z
Learning: In the Request Network codebase, pagination is handled at a higher level in the architecture, not in the HTTP data access layer. This architectural decision was made to ensure correct handling of decrypted requests in paginated results.

Applied to files:

• README.md

📚 Learning: 2024-11-04T20:53:41.522Z

Learnt from: giorgi-kiknavelidze
Repo: RequestNetwork/requestNetwork PR: 1482
File: packages/payment-processor/src/payment/prepare-hinkal.ts:5-13
Timestamp: 2024-11-04T20:53:41.522Z
Learning: When reviewing the RequestNetwork codebase, avoid suggesting the addition of example usage in documentation if it would make the comments overly verbose, especially for functions like `prepareHinkal` in `packages/payment-processor/src/payment/prepare-hinkal.ts`.

Applied to files:

• README.md

🔇 Additional comments (1)

README.md (1)

7-7: LGTM! Badge restoration looks good.

The change replaces the broken dynamic CodeRabbit PR-count badge with a reliable static badge that links to CodeRabbit's website. The markdown syntax is correct, the shields.io badge URL format is standard and valid, and the link destination is appropriate.

---

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

[MantisClone]

Hello @Olexandr88, thank you for submitting your first pull request to the requestNetwork repository. We value your contribution and encourage you to review our contribution guidelines to ensure your submission meets our standards. Please note that every merged PR is automatically enrolled in our Best PR Initiative, offering a chance to win $500 each quarter. Our team is available via GitHub Discussions or Discord if you have any questions. Welcome aboard!

[MantisClone]

Thank you for your submission! As you prepare for the review process, please ensure that your PR title, description, and any linked issues fully comply with our contribution guidelines. A clear explanation of your changes and their context will help expedite the review process. Every merged PR is automatically entered into our Best PR Initiative, offering a chance to win $500 every quarter. We appreciate your attention to detail and look forward to reviewing your contribution!