chore: remove email from code of conduct

[TomerFi]

Remove email address from Code of Conduct Enforcement section, replacing with "via GitHub" for consistency across projects.

• Change applied
• Verified consistency

Summary by Sourcery

Documentation:

• Clarify the enforcement contact instructions in the Code of Conduct by directing users to contact the project team via GitHub rather than email.

Summary by CodeRabbit

• Documentation
  • Updated Code of Conduct reporting method to direct complaints via GitHub profiles instead of a direct email; existing statements about review, confidentiality and complaint handling remain unchanged.

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

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the Code of Conduct enforcement contact method to use GitHub instead of a direct email address for reporting incidents.

File-Level Changes

Change	Details	Files
Update Code of Conduct enforcement contact instructions to route reports via GitHub instead of a personal email address.	Replace the explicit email address contact with a generic "via GitHub" phrasing in the Enforcement section text Keep all surrounding enforcement policy language and structure unchanged to preserve existing behavior and meaning	.github/CODE_OF_CONDUCT.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request updates the Code of Conduct Enforcement section by replacing the email contact method with a GitHub-based reporting mechanism, preserving the remainder of the enforcement text and procedures.

Changes

Cohort / File(s)	Summary
Documentation Update .github/CODE_OF_CONDUCT.md	Replaced email contact with GitHub profile/DM-based reporting in the Enforcement section (two instances).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐇 I hopped a note from mail to GH,

Reporting now via profiles we see,
A tiny change, a clearer way,
Community care in bright display,
— from a rabbit, cheers for harmony.

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 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: removing an email address from the Code of Conduct file, which matches the actual modification shown in the summary.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ 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
• Commit unit tests in branch chore/remove-email-from-coc

---

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

[github-actions]

Test Results

66 tests   66 ✅  1s ⏱️
 1 suites   0 💤
 1 files     0 ❌

Results for commit 9aa35df.

♻️ This comment has been updated with latest results.

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 96.02%. Comparing base (4df5059) to head (9aa35df).
⚠️ Report is 1 commits behind head on dev.

Additional details and impacted files

@@           Coverage Diff           @@
##              dev     #941   +/-   ##
=======================================
  Coverage   96.02%   96.02%           
=======================================
  Files           1        1           
  Lines         327      327           
=======================================
  Hits          314      314           
  Misses         13       13           

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In @.github/CODE_OF_CONDUCT.md:
- Line 56: Summary: The phrase "via GitHub" is too vague; update the
CODE_OF_CONDUCT.md to specify the exact GitHub reporting mechanism. Replace the
vague "via GitHub" wording with a single explicit instruction: state whether
reporters should open a GitHub Issue (and which template/label to use), post in
GitHub Discussions (and which category), or contact maintainers via direct
GitHub profiles; if a confidential channel exists, point to the GitHub Security
Advisory form or provide the private contact method. Ensure the revised sentence
references the original phrase "via GitHub" so reviewers can locate and replace
it, and include a short parenthetical about confidentiality if using a public
channel.

[TomerFi]

@coderabbitai resolve

[coderabbitai]

✅ Actions performed

Comments resolved.