Docs fix repo paths in contributing 361

[NssGourav]

Related Issue

Closes: #361

Describe the changes you've made

This PR corrects the repo paths in CONTRIBUTING.md so contributors can follow the right structure and avoid future merge conflicts.

How has this been tested?

I have tested it manually by comparing the new version and the older version of the branch.

Checklist

• I have performed a self-review of my own code.
• I have commented on my code, particularly wherever it was hard to understand.
• I have made corresponding changes to the documentation.
• I have followed the code style of the project
• I have tested my code, and it works without errors

Additional Information

Code of Conduct

• I agree to follow this project's Code of Conduct

Summary by CodeRabbit

• Documentation
  • Corrected contributor setup instructions to reference the proper repository.
  • Updated README: refreshed supporter heading and replaced the GitHub stars/stargazer badge with an updated badge pointing to the correct project.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Updated documentation: corrected git clone and cd commands in CONTRIBUTING.md to reference the reseter.css repository; adjusted README.md supporter heading emoji and replaced the GitHub Stargazers badge line with a GitHub Stars badge pointing to a different repository URL.

Changes

Cohort / File(s)	Summary
Documentation path corrections CONTRIBUTING.md	Updated git clone and cd commands to reference the reseter.css repository instead of gardevoir. Branch naming and workflow steps unchanged.
README documentation updates README.md	Changed "## ❤ Thanks to our supporters" emoji to "## ❤️ Thanks to our supporters"; replaced the "GitHub Stargazers" badge line with a "GitHub Stars" badge line pointing to a different repository URL.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

• Simple documentation and path updates only
• Files to spot-check: CONTRIBUTING.md, README.md

Poem

🐰 I hopped through lines of text so neat,
I nudged the path to reseter.css's seat,
I swapped a heart and peeked at stars above,
A tiny rabbit praising docs with love. ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Out of Scope Changes check	⚠️ Warning	README.md changes (badge update and emoji fix) are not required by issue #361, which specifically targets CONTRIBUTING.md repository path corrections.	Remove README.md changes from this PR or create a separate PR for documentation improvements unrelated to the repository path fixes in CONTRIBUTING.md.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title directly references the main change: fixing repository paths in CONTRIBUTING.md as described in issue #361.
Linked Issues check	✅ Passed	The PR addresses issue #361 by updating repository paths in CONTRIBUTING.md and also improves README.md clarity, meeting the objectives to fix references and enable proper contributor setup.
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 9642422 and 9d6d0c0.

📒 Files selected for processing (1)

• README.md (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• README.md

---

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

[NssGourav]

@kkrishguptaa @Roshanjossey Please Review it and tell me if any changes required to merge , Thanks.

[NssGourav]

@gptkrsh can you look at the pr

[Roshanjossey]

@NssGourav, I'm not a maintainer here, so I can't review.

Please wait for @kkrishguptaa to review. This might take time in open source projects. You have to be patient.

[NssGourav]

@kkrishguptaa @gptkrsh please can you review my pr

[kkrishguptaa]

Hi! Thank you for submitting this PR, sorry for the delayed response.