Skip to content

docs: add contributor code of conduct#546

Merged
zachyale merged 1 commit into
developfrom
docs/add-code-of-conduct
Apr 16, 2026
Merged

docs: add contributor code of conduct#546
zachyale merged 1 commit into
developfrom
docs/add-code-of-conduct

Conversation

@zachyale

@zachyale zachyale commented Apr 16, 2026 •
edited by coderabbitai Bot
Loading

Copy link
Copy Markdown
Member

Description

This PR adds a repository-level contributor code of conduct by introducing a standard
Contributor Covenant policy for the Grimmory community.

The new document defines expected behaviour, unacceptable conduct, scope, enforcement
responsibilities, reporting guidance, and escalation outcomes so contributors and
maintainers have a clear shared standard for community participation.

Changes

  • Add a root CODE_OF_CONDUCT.md
  • Adopt the Contributor Covenant Code of Conduct
  • Define community behaviour standards/unacceptable conduct
  • Add reporting and enforcement guidance for maintainers and contributors

Summary by CodeRabbit

  • Chores
    • Added a Code of Conduct document that establishes community expectations, defines standards for respectful participation, and outlines enforcement procedures for maintaining an inclusive and harassment-free environment.

@coderabbitai

coderabbitai Bot commented Apr 16, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 0dc2a954-3e57-4add-9b10-44afc5b175fe

📥 Commits

Reviewing files that changed from the base of the PR and between e087972 and d911460.

📒 Files selected for processing (1)
  • CODE_OF_CONDUCT.md
📜 Recent review details
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (6)
  • GitHub Check: Test Suite / Backend Tests
  • GitHub Check: Test Suite / Frontend Tests
  • GitHub Check: Analyze (javascript-typescript)
  • GitHub Check: Analyze (actions)
  • GitHub Check: Analyze (java-kotlin)
  • GitHub Check: Frontend Lint Threshold Check
🧰 Additional context used
🪛 LanguageTool
CODE_OF_CONDUCT.md

[style] ~32-~32: Try using a synonym here to strengthen your wording.
Context: ...ind - Trolling, insulting or derogatory comments, and personal or political attacks - Pu...

(COMMENT_REMARK)

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

1-129: Clean and complete Code of Conduct adoption.

This is a solid addition: the policy covers behavior standards, scope, reporting, enforcement, and attribution clearly, and aligns with the PR objective.

📝 Walkthrough

Walkthrough

A new CODE_OF_CONDUCT.md file has been added to the repository, establishing community standards, behavioral expectations, and enforcement procedures. The document outlines conduct guidelines, reporting mechanisms, and tiered enforcement actions for maintainers.

Changes

Cohort / File(s) Summary
Community Governance
CODE_OF_CONDUCT.md		 Added comprehensive code of conduct document defining community expectations, pledge of inclusive participation, examples of acceptable and unacceptable behavior, reporting procedures via maintainer email, and tiered enforcement guidelines (Correction, Warning, Temporary Ban, Permanent Ban).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Suggested labels

chore

Poem

🐰 A warren of kindness, we hop into place,
With conduct and care, at a measured pace,
Respect blooms like clover in our shared space,
Where everyone's welcome, with dignity and grace! 🌱

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The PR title 'docs: add contributor code of conduct' follows the conventional commit format with the 'docs:' prefix and clearly describes the change.
Description check ✅ Passed The PR description includes all required template sections (Description and Changes) with substantive content explaining the purpose and listing specific changes made.
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
  • Commit unit tests in branch docs/add-code-of-conduct
✨ Simplify code
  • Create PR with simplified code
  • Commit simplified code in branch docs/add-code-of-conduct

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.

@coderabbitai coderabbitai Bot added the chore label Apr 16, 2026
balazs-szucs
balazs-szucs approved these changes Apr 16, 2026
View reviewed changes

@balazs-szucs balazs-szucs left a comment

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.

👍

@zachyale zachyale merged commit 5ac0f63 into develop Apr 16, 2026
17 checks passed
@zachyale zachyale deleted the docs/add-code-of-conduct branch April 16, 2026 17:53
zachyale added a commit to zachyale/grimmory that referenced this pull request Apr 17, 2026
@zachyale
docs: add code of conduct (grimmory-tools#546)
b4a30f0
zachyale added a commit to zachyale/grimmory that referenced this pull request Apr 17, 2026
@zachyale
docs: add code of conduct (grimmory-tools#546)
be4904a
zachyale added a commit that referenced this pull request Apr 17, 2026
@zachyale
docs: add code of conduct (#546)
b69494b
zachyale added a commit that referenced this pull request Apr 22, 2026
@zachyale
docs: add code of conduct (#546)
4c56e10
dsmouse pushed a commit to dsmouse/grimmory that referenced this pull request May 11, 2026
@zachyale
docs: add code of conduct (grimmory-tools#546)
4a4d891
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

1 more reviewer

@balazs-szucs balazs-szucs balazs-szucs approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

chore

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@zachyale @balazs-szucs