Skip to content

docs: add CONTRIBUTING.md to align with open-source best practices#21

Closed
Vaishnavi10706 wants to merge 3 commits intoAOSSIE-Org:mainfrom
Vaishnavi10706:docs/add-contributing-guidelines
Closed

docs: add CONTRIBUTING.md to align with open-source best practices#21
Vaishnavi10706 wants to merge 3 commits intoAOSSIE-Org:mainfrom
Vaishnavi10706:docs/add-contributing-guidelines

Conversation

@Vaishnavi10706
Copy link
Copy Markdown
Contributor

@Vaishnavi10706 Vaishnavi10706 commented Feb 15, 2026

Summary

This PR adds a CONTRIBUTING.md file to the SocialShareButton repository to align it with open-source best practices followed across the organization.

What’s Included

  • Contribution workflow guidelines
  • Branch naming conventions
  • Development guidelines
  • Pull request process instructions

Why This Change

The repository currently lacks a standardized contribution guide. Adding this file improves contributor onboarding, ensures consistency, and enhances maintainability.

This PR implements only one best practice as per the issue instructions.

Summary by CodeRabbit

  • Documentation
    • Added comprehensive contributing guidelines covering how to start and track issues, local setup and getting-started steps (fork, clone, install, branch creation), branch naming conventions, development standards and workflow for making changes, pull request submission process, and a Code of Conduct to guide community contributions.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Feb 15, 2026

Warning

Rate limit exceeded

@Vaishnavi10706 has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 11 minutes and 13 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📝 Walkthrough

Walkthrough

A new CONTRIBUTING.md file was added, providing contributor guidelines for SocialShareButton covering pre-start checks, setup (fork/clone/install), branch naming conventions, development practices, PR submission steps, and a Code of Conduct.

Changes

Cohort / File(s) Summary
Contributor Documentation
CONTRIBUTING.md
Added a comprehensive contribution guide including pre-start checks, setup instructions, branch naming conventions, development and commit guidelines, PR checklist, Code of Conduct, and contributor acknowledgement.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 I hopped in with a guide so bright,
Branches named and PRs in sight,
Fork, clone, code — then send with care,
A little hop to help you share,
Thank you, friends, for every byte!

🚥 Pre-merge checks | ✅ 4
✅ 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 clearly describes the main change: adding a CONTRIBUTING.md file to align with open-source best practices, which directly matches the changeset.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Merge Conflict Detection ✅ Passed ✅ No merge conflicts detected when merging into main

✏️ 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

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

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

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🤖 Fix all issues with AI agents
In `@CONTRIBUTING.md`:
- Around line 19-28: Wrap all inline shell commands in fenced code blocks using
the bash language (e.g., replace the inline "git clone
https://github.com/your-username/SocialShareButton.git", "cd SocialShareButton",
"npm install", "git checkout -b feature/your-feature-name", and "git push origin
feature/your-feature-name" with fenced blocks like ```bash\ngit clone ...\n```)
so each numbered step shows its command in a clear, copyable code block; apply
the same fenced-block formatting to the instances referenced at lines 57-58 as
well.
- Around line 67-69: Update the "## 🧑‍💻 Code of Conduct" section to reference
the actual file by name and provide a link to it (e.g., point to
CODE_OF_CONDUCT.md) so contributors can locate the document; edit the line that
currently reads "Please follow the project's Code of Conduct and maintain
respectful and inclusive communication." to include a direct reference such as
"Please read our Code of Conduct (CODE_OF_CONDUCT.md) for details on respectful
and inclusive communication." to make the location explicit.

Comment thread CONTRIBUTING.md
Comment thread CONTRIBUTING.md
Comment on lines +67 to +69
## 🧑‍💻 Code of Conduct

Please follow the project's Code of Conduct and maintain respectful and inclusive communication.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Link to the Code of Conduct file.

Please reference the actual file (e.g., CODE_OF_CONDUCT.md) so contributors know exactly where to read it.

💡 Suggested wording
-Please follow the project's Code of Conduct and maintain respectful and inclusive communication.
+Please follow the project's Code of Conduct (see `CODE_OF_CONDUCT.md`) and maintain respectful and inclusive communication.
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
## 🧑‍💻 Code of Conduct
Please follow the project's Code of Conduct and maintain respectful and inclusive communication.
## 🧑‍💻 Code of Conduct
Please follow the project's Code of Conduct (see `CODE_OF_CONDUCT.md`) and maintain respectful and inclusive communication.
🤖 Prompt for AI Agents
In `@CONTRIBUTING.md` around lines 67 - 69, Update the "## 🧑‍💻 Code of Conduct"
section to reference the actual file by name and provide a link to it (e.g.,
point to CODE_OF_CONDUCT.md) so contributors can locate the document; edit the
line that currently reads "Please follow the project's Code of Conduct and
maintain respectful and inclusive communication." to include a direct reference
such as "Please read our Code of Conduct (CODE_OF_CONDUCT.md) for details on
respectful and inclusive communication." to make the location explicit.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Fix all issues with AI agents
In `@CONTRIBUTING.md`:
- Around line 89-97: Remove the accidental triple-backtick fenced block around
the Code of Conduct section in CONTRIBUTING.md so the heading "## 🧑‍💻 Code of
Conduct" and its paragraph render as normal Markdown; simply delete the opening
and closing ```markdown``` fences and ensure the heading, paragraph, horizontal
rule (---) and closing thank-you line remain as plain Markdown.

Comment thread CONTRIBUTING.md Outdated
@kpj2006
Copy link
Copy Markdown
Contributor

kpj2006 commented Feb 18, 2026

mention issue in pr: #18

@amankv1234 already pick this up, you should move on to another file adding since there are multiple file to be added in this issue.

@Vaishnavi10706
Copy link
Copy Markdown
Contributor Author

mention issue in pr: #18

@amankv1234 already pick this up, you should move on to another file adding since there are multiple file to be added in this issue.

@kpj2006
Thanks for the clarification! I’ll close this PR and work on adding another file instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants