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

Create CODE_OF_CONDUCT.md #191

Closed
wants to merge 1 commit into from

Conversation

PelinSmines
Copy link

@PelinSmines PelinSmines commented Aug 30, 2024

We added the code of conduct based on the contributor covenant.
This is fixing partially the issue #104
Added the contact info as [email protected]. Please do check and update in the Code of Conduct as you fir appropriate.

Summary by Sourcery

Introduce a Code of Conduct based on the Contributor Covenant to promote a harassment-free community experience and outline enforcement responsibilities and guidelines.

Documentation:

  • Add a Contributor Covenant Code of Conduct to establish community standards and guidelines for behavior.

We added the code of conduct based on the contributor covenant.
Copy link

sourcery-ai bot commented Aug 30, 2024

Reviewer's Guide by Sourcery

This pull request adds a new file CODE_OF_CONDUCT.md to the repository, implementing a Code of Conduct based on the Contributor Covenant version 2.0. The code of conduct outlines the expected behavior, enforcement responsibilities, and guidelines for the community.

File-Level Changes

Change Details Files
Addition of a Code of Conduct file
  • Implemented the Contributor Covenant Code of Conduct version 2.0
  • Defined the community's pledge for a harassment-free experience
  • Outlined examples of positive and unacceptable behavior
  • Specified enforcement responsibilities and guidelines
  • Included contact information for reporting violations ([email protected])
  • Added attribution and links to the original Contributor Covenant
CODE_OF_CONDUCT.md

Tips
  • Trigger a new Sourcery review by commenting @sourcery-ai review on the pull request.
  • Continue your discussion with Sourcery by replying directly to review comments.
  • You can change your review settings at any time by accessing your dashboard:
    • Enable or disable the Sourcery-generated pull request summary or reviewer's guide;
    • Change the review language;
  • You can always contact us if you have any questions or feedback.

Copy link

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

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

Hey @PelinSmines - I've reviewed your changes - here's some feedback:

Overall Comments:

  • Consider using a dedicated email address for Code of Conduct issues instead of the general [email protected].
  • Could you clarify what you mean by 'Please do check and update in the Code of Conduct as you fir appropriate' in the description? There seems to be a typo or unfinished thought there.
  • The description mentions this PR partially fixes an issue. Could you elaborate on what aspects of the issue remain unaddressed?
Here's what I looked at during the review
  • 🟢 General issues: all looks good
  • 🟢 Security: all looks good
  • 🟢 Testing: all looks good
  • 🟢 Complexity: all looks good
  • 🟡 Documentation: 1 issue found

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment to tell me if it was helpful.


Instances of abusive, harassing, or otherwise unacceptable behavior may be
reported to the community leaders responsible for enforcement at
[[email protected]].
Copy link

Choose a reason for hiding this comment

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

nitpick (documentation): Consider removing square brackets around the email address.

@mariobehling
Copy link
Member

Thanks. This issue will be taken care of by core team members. It is not suitable for a newbie.

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