Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update CODE_OF_CONDUCT.md #372

Merged
merged 1 commit into from
Oct 21, 2024
Merged

Conversation

Nikhil0-3
Copy link
Contributor

@Nikhil0-3 Nikhil0-3 commented Oct 21, 2024

As per the issue #371 I update the file with all require changes

I added the following topics -
How to contribute (fix bugs, add features)
Steps for submitting changes
Project setup instructions
Rules for code style
Code of conduct for respectful behavior
Enhance the project structure
Add the help and support section
Add the pull request section
Add issue report process section

Also , I tried to make ik more interative.
If any further changes required please tell me.

Summary by CodeRabbit

  • New Features

    • Introduced a revamped Contributor Covenant Code of Conduct with enhanced clarity and inclusivity.
    • Added new sections, including "📋Pull Request Guidelines" outlining contribution expectations.
  • Improvements

    • Improved formatting with headings and emojis for better visual appeal.
    • Refined language in various sections to enhance readability and promote a positive community environment.

Copy link

vercel bot commented Oct 21, 2024

@Nikhil0-3 is attempting to deploy a commit to the bunty's projects Team on Vercel.

A member of the Team first needs to authorize it.

Copy link
Contributor

coderabbitai bot commented Oct 21, 2024

Walkthrough

The changes in this pull request involve a comprehensive restructuring and enhancement of the CODE_OF_CONDUCT.md file. The document's title has been updated to "✨Contributor Covenant Code of Conduct✨," and various sections have been renamed and reformatted for improved clarity and inclusivity. New sections such as "Our Pledge," "Pull Request Guidelines," and updated enforcement responsibilities have been introduced to foster a more positive community environment. The overall aim is to make the document more accessible and user-friendly.

Changes

File Change Summary
CODE_OF_CONDUCT.md - Title changed to "✨Contributor Covenant Code of Conduct✨".
- Sections renamed and restructured for clarity (e.g., "Our Pledge," "Scope," "Enforcement").
- Added "📋Pull Request Guidelines" section.
- Enhanced language for inclusivity and readability.

Possibly related issues

Possibly related PRs

  • Created CODE_OF_CONDUCT.md #126: This PR introduces a CODE_OF_CONDUCT.md file, which is directly related to the modifications made in the current PR, focusing on clarity and inclusivity.

Suggested labels

documentation, level1, gssoc-ext

Poem

🐰 In the garden where we play,
A code of conduct lights the way.
With pledges bright and standards clear,
We build a space where all can cheer!
So hop along, let kindness bloom,
Together we can chase the gloom! 🌼


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

Thank you for submitting your pull request! 🙌 We'll review it as soon as possible. In the meantime, please ensure that your changes align with our CONTRIBUTING.md. If there are any specific instructions or feedback regarding your PR, we'll provide them here. Thanks again for your contribution! 😊

Copy link
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: 0

🧹 Outside diff range and nitpick comments (4)
CODE_OF_CONDUCT.md (4)

18-40: Excellent articulation of community standards!

The clear distinction between positive and negative behaviors, coupled with the use of emojis, makes this section highly effective. The examples provided are comprehensive and well-articulated.

Consider adding a brief introductory sentence before the positive behaviors list to mirror the structure of the negative behaviors list. For example:

Examples of behavior that contributes to a positive environment for our
community include:

+ The following actions are encouraged to foster a welcoming atmosphere:

* 💖Demonstrating empathy and kindness toward other people
...
🧰 Tools
🪛 LanguageTool

[style] ~35-~35: Try using a synonym here to strengthen your wording.
Context: ...d * 🛑Trolling, insulting or derogatory comments, and personal or political attacks * ⚠️...

(COMMENT_REMARK)


66-71: Valuable addition of Pull Request Guidelines!

The inclusion of this new section aligns well with the PR objectives and provides clear expectations for contributors. It's a great addition to the document.

To make this section even more helpful, consider adding specific examples of what constitutes appropriate and inappropriate behavior in pull requests. For instance:

Contributions, including pull requests, must align with this Code of Conduct. 
All contributors are expected to submit work that fosters a positive and inclusive community. 
Inappropriate behavior, language, or content in pull requests may result in the rejection of 
the contribution and further enforcement actions as outlined in the guidelines.

+ Examples of appropriate behavior in pull requests include:
+ * Providing clear and constructive feedback
+ * Acknowledging and appreciating others' contributions
+ * Being open to suggestions and criticism
+
+ Examples of inappropriate behavior in pull requests include:
+ * Using offensive or derogatory language
+ * Personally attacking or insulting other contributors
+ * Spamming or trolling in comments

132-145: Proper attribution and helpful resources!

The renaming to "📜Attribution" and the comprehensive credit to the Contributor Covenant and Mozilla's code of conduct are excellent. The inclusion of links to FAQs and translations is very helpful.

Consider formatting the bare URLs as proper markdown links for better readability and to adhere to markdown best practices. For example:

- https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+ [https://www.contributor-covenant.org/version/2/0/code_of_conduct.html](https://www.contributor-covenant.org/version/2/0/code_of_conduct.html).

- https://www.contributor-covenant.org/faq. Translations are available at
- https://www.contributor-covenant.org/translations.
+ [https://www.contributor-covenant.org/faq](https://www.contributor-covenant.org/faq). Translations are available at
+ [https://www.contributor-covenant.org/translations](https://www.contributor-covenant.org/translations).
🧰 Tools
🪛 LanguageTool

[uncategorized] ~137-~137: You might be missing the article “the” here.
Context: ....org/version/2/0/code_of_conduct.html. Community Impact Guidelines were inspired by [Moz...

(AI_EN_LECTOR_MISSING_DETERMINER_THE)

🪛 Markdownlint

136-136: null
Bare URL used

(MD034, no-bare-urls)


144-144: null
Bare URL used

(MD034, no-bare-urls)


145-145: null
Bare URL used

(MD034, no-bare-urls)


137-137: Minor grammar improvement

To enhance readability, consider adding the article "the" before "Community Impact Guidelines":

- Community Impact Guidelines were inspired by [Mozilla's code of conduct
+ The Community Impact Guidelines were inspired by [Mozilla's code of conduct
🧰 Tools
🪛 LanguageTool

[uncategorized] ~137-~137: You might be missing the article “the” here.
Context: ....org/version/2/0/code_of_conduct.html. Community Impact Guidelines were inspired by [Moz...

(AI_EN_LECTOR_MISSING_DETERMINER_THE)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 8fbf6c1 and 97481e4.

📒 Files selected for processing (1)
  • CODE_OF_CONDUCT.md (1 hunks)
🧰 Additional context used
🪛 LanguageTool
CODE_OF_CONDUCT.md

[style] ~35-~35: Try using a synonym here to strengthen your wording.
Context: ...d * 🛑Trolling, insulting or derogatory comments, and personal or political attacks * ⚠️...

(COMMENT_REMARK)


[uncategorized] ~137-~137: You might be missing the article “the” here.
Context: ....org/version/2/0/code_of_conduct.html. Community Impact Guidelines were inspired by [Moz...

(AI_EN_LECTOR_MISSING_DETERMINER_THE)

🪛 Markdownlint
CODE_OF_CONDUCT.md

136-136: null
Bare URL used

(MD034, no-bare-urls)


144-144: null
Bare URL used

(MD034, no-bare-urls)


145-145: null
Bare URL used

(MD034, no-bare-urls)

🔇 Additional comments (5)
CODE_OF_CONDUCT.md (5)

1-16: Great improvements to the title and introduction!

The addition of emojis and the new "Our Pledge" section significantly enhances the document's appeal and sets a positive, inclusive tone right from the start. The pledge effectively emphasizes the commitment to a harassment-free environment for all contributors.


44-54: Well-defined enforcement responsibilities!

The renaming of this section to "👨‍⚖️Enforcement Responsibilities" and the clear articulation of community leaders' roles strengthen the document. The language used effectively communicates the authority and responsibilities of those enforcing the Code of Conduct.


56-63: Clear and comprehensive scope definition!

The renaming to "🌐Scope" and the clear explanation of where the Code of Conduct applies are excellent additions. The examples provided for representing the community are relevant and help users understand the extent of the code's application.


74-129: Comprehensive and well-structured enforcement guidelines!

The renaming of the "Enforcement" section and the addition of the detailed "Enforcement Guidelines" significantly improve the document. The clear escalation path with defined community impacts and consequences for each level provides a transparent and fair approach to handling violations.


1-145: Excellent update to the Code of Conduct!

This comprehensive revision significantly enhances the document's clarity, inclusivity, and appeal. The addition of emojis, clear section divisions, and detailed guidelines for behavior and enforcement create a more engaging and effective Code of Conduct. The changes align perfectly with the PR objectives and modern open-source community standards.

A few minor suggestions have been made to further improve specific sections, but overall, this update is a substantial improvement that will greatly benefit the project and its contributors.

Great work on this important document!

🧰 Tools
🪛 LanguageTool

[style] ~35-~35: Try using a synonym here to strengthen your wording.
Context: ...d * 🛑Trolling, insulting or derogatory comments, and personal or political attacks * ⚠️...

(COMMENT_REMARK)


[uncategorized] ~137-~137: You might be missing the article “the” here.
Context: ....org/version/2/0/code_of_conduct.html. Community Impact Guidelines were inspired by [Moz...

(AI_EN_LECTOR_MISSING_DETERMINER_THE)

🪛 Markdownlint

136-136: null
Bare URL used

(MD034, no-bare-urls)


144-144: null
Bare URL used

(MD034, no-bare-urls)


145-145: null
Bare URL used

(MD034, no-bare-urls)

Copy link
Owner

@RamakrushnaBiswal RamakrushnaBiswal left a comment

Choose a reason for hiding this comment

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

LGTM

@RamakrushnaBiswal RamakrushnaBiswal merged commit 7e38315 into RamakrushnaBiswal:main Oct 21, 2024
4 of 5 checks passed
@RamakrushnaBiswal RamakrushnaBiswal added documentation Improvements or additions to documentation good first issue Good for newcomers level1 for 10 points gssoc-ext gssoc-extd program hacktoberfest accepted hacktoberfest-accepted repo labels Oct 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation good first issue Good for newcomers gssoc-ext gssoc-extd program hacktoberfest accepted hacktoberfest-accepted repo level1 for 10 points
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants