Add CODE_OF_CONDUCT.md

[faizakhtar-000]

Added a CODE_OF_CONDUCT.md file to define community guidelines and maintain a respectful environment for contributors.
closure #323

Summary by CodeRabbit

• Documentation
  • Added a comprehensive Code of Conduct establishing community standards, behavioral expectations, reporting procedures, and enforcement guidelines for project contributors and participants.

[coderabbitai]

📝 Walkthrough

Walkthrough

CODE_OF_CONDUCT.md is added with a complete, structured document that defines community standards, expected behaviors, unacceptable conduct, enforcement consequences, contributor and maintainer responsibilities, applicable scope, and reporting procedures for violations.

Changes

Community Code of Conduct

Layer / File(s)	Summary
Code of Conduct document CODE_OF_CONDUCT.md	CODE_OF_CONDUCT.md is added with complete sections covering project commitment to inclusivity, expected community behaviors, examples of unacceptable conduct, enforcement outcomes, contributor and maintainer responsibilities, scope of applicability, and violation reporting procedures.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

A warren of voices, all welcomed with care,
Guidelines and kindness now written so fair,
From contribution to comment, we treat all the same,
Building community—that is the game! 🐰✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Add CODE_OF_CONDUCT.md' directly and accurately describes the main change in the pull request, which adds a new CODE_OF_CONDUCT.md file to the project.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[coderabbitai]

🧹 Nitpick comments (1)

CODE_OF_CONDUCT.md (1)

62-66: ⚡ Quick win

Add a concrete reporting channel in the incident-reporting section.

“Report it to the project maintainers” is ambiguous in practice. Please include at least one explicit route (email, issue form, or private channel) and expected response window.
[Suggesting this now prevents confusion during time-sensitive incidents.]

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@CODE_OF_CONDUCT.md` around lines 62 - 66, Update the "## Reporting Issues"
section to replace the ambiguous "report it to the project maintainers" with a
concrete reporting channel and response window: add at least one explicit route
(e.g., a dedicated email address or a link to a private incident report form)
and specify the expected acknowledgement/response timeframe (for example "we
will acknowledge reports within 48 hours and provide an initial update within 5
business days"). Ensure the text remains respectful/confidential and clearly
labels the contact method (e.g., "Email: security@example.com" or "Report form:
<link>") so maintainers and reporters know exactly how to submit incidents and
what response to expect.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@CODE_OF_CONDUCT.md`:
- Around line 62-66: Update the "## Reporting Issues" section to replace the
ambiguous "report it to the project maintainers" with a concrete reporting
channel and response window: add at least one explicit route (e.g., a dedicated
email address or a link to a private incident report form) and specify the
expected acknowledgement/response timeframe (for example "we will acknowledge
reports within 48 hours and provide an initial update within 5 business days").
Ensure the text remains respectful/confidential and clearly labels the contact
method (e.g., "Email: security@example.com" or "Report form: <link>") so
maintainers and reporters know exactly how to submit incidents and what response
to expect.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: d4e63918-eb7d-4deb-8da2-7bb6b4c77a14

📥 Commits

Reviewing files that changed from the base of the PR and between 3552efa and 0b0e23e.

📒 Files selected for processing (1)

• CODE_OF_CONDUCT.md