Skip to content

Comments

add email to CODE_OF_CONDUCT.md#98

Merged
izadoesdev merged 1 commit intodatabuddy-analytics:mainfrom
EverStarck:patch-2
Aug 18, 2025
Merged

add email to CODE_OF_CONDUCT.md#98
izadoesdev merged 1 commit intodatabuddy-analytics:mainfrom
EverStarck:patch-2

Conversation

@EverStarck
Copy link
Contributor

@EverStarck EverStarck commented Aug 18, 2025

im gonna steal this file btw

Pull Request

Description

Please include a summary of the change and which issue is fixed. Also include relevant motivation and context.

Checklist

  • My code follows the style guidelines of this project
  • I have performed a self-review of my code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes

Summary by CodeRabbit

  • Documentation
    • Updated the Code of Conduct to include a dedicated enforcement contact email (support@databuddy.cc), replacing the previous placeholder.
    • Clarifies how to report violations and request assistance, improving transparency and accessibility for community members.
    • No functional changes to the product; this update refines community guidance and support information.

im gonna steal this file btw
@vercel
Copy link

vercel bot commented Aug 18, 2025

@EverStarck is attempting to deploy a commit to the Databuddy Team on Vercel.

A member of the Team first needs to authorize it.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Aug 18, 2025

Walkthrough

The enforcement contact email in CODE_OF_CONDUCT.md was updated from a placeholder to support@databuddy.cc. No other content or functional code was changed.

Changes

Cohort / File(s) Summary of Changes
Documentation — Code of Conduct
CODE_OF_CONDUCT.md
Replaced placeholder enforcement contact email with support@databuddy.cc; all other sections unchanged.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

I twitch my ears at tidy text,
A contact line now neatly fixed.
Support awaits—so clear, concise—
A carrot-check for playing nice.
Hop hop hooray, the doc’s in sync,
Less guess, more help, in just one blink. 🥕✨

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

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
🪧 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.
    • 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.
  • 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

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

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • 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.

@graphite-app
Copy link
Contributor

graphite-app bot commented Aug 18, 2025

How to use the Graphite Merge Queue

Add the label Main to this PR to add it to the merge queue.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

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

🧹 Nitpick comments (2)
CODE_OF_CONDUCT.md (2)

21-21: Wrap email as a Markdown mailto link to satisfy markdownlint (MD034).

markdownlint is flagging a "bare URL" on this line. Converting the plain email into a mailto link both improves UX and quiets the linter.

-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at support@databuddy.cc. All complaints will be reviewed and investigated.
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [support@databuddy.cc](mailto:support@databuddy.cc). All complaints will be reviewed and investigated.

Follow-up:

  • Please confirm that this inbox is monitored by the Code of Conduct responders and suitable for sensitive reports (group alias preferred over an individual).

24-24: Tighten attribution: specify Contributor Covenant version and remove trailing whitespace.

Referencing the exact version is standard and makes the source explicit. Also removes trailing whitespace at end of line.

-This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org/). 
+This Code of Conduct is adapted from the [Contributor Covenant v2.1](https://www.contributor-covenant.org/version/2/1/code_of_conduct/).
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between b2a94fd and d6aca13.

📒 Files selected for processing (1)
  • CODE_OF_CONDUCT.md (1 hunks)
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
CODE_OF_CONDUCT.md

21-21: Bare URL used

(MD034, no-bare-urls)

⏰ 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). (1)
  • GitHub Check: Analyze (javascript-typescript)

@izadoesdev
Copy link
Member

i was gonna add this but forgor lol, nice

@izadoesdev izadoesdev merged commit 7075d95 into databuddy-analytics:main Aug 18, 2025
6 of 9 checks passed
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