Conversation
Clarified rules regarding threats and conspiracy theories, and added examples of low-quality messages.
Update server rules for clarity and examples
|
Related Documentation Checked 0 published document(s) in 1 knowledge base(s). No updates required. How did I do? Any feedback? |
Summary of ChangesHello @YINGVAY, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request refines the Code of Conduct by improving the organization of existing rules and providing more explicit examples for chat quality guidelines. The changes aim to enhance clarity and ensure a more consistent understanding of expected behavior within the community, particularly regarding content and communication standards. Highlights
Changelog
Activity
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
📝 WalkthroughWalkthroughUpdated Code of Conduct documentation in README.md by removing explicit conspiracy theory prohibition mention in Mutual Respect section, expanding the Controversial and Sensitive Topics section to include ongoing global conflicts and historical topics with defined subsection, and adding explicit Chat Quality examples with moderator intervention guidance. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Suggested labels
Suggested reviewers
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Tip Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord. 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. Comment |
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
The pull request updates the Code of Conduct by moving the conspiracy theory prohibition to a more appropriate section and adding specific examples of low-quality messages. However, these changes are made directly to the generated README.md instead of the source TOML files (code_of_conduct/sections/), which will lead to synchronization issues. Additionally, there is a minor typo in the new examples.
| Maintain a respectful and humble attitude in all interactions. Avoid displaying unwarranted arrogance or belittling others. Any form of discrimination towards other members based on their unique characteristics is strictly prohibited. Unique characteristics are, but aren't limited to: race, age, gender, sexual orientation, and religion. | ||
|
|
||
| Threats, regardless of whether they are direct, indirect, or implied, will not be tolerated. Conspiracy theories are also prohibited. | ||
| Threats, regardless of whether they are direct, indirect, or implied, will not be tolerated. |
There was a problem hiding this comment.
The changes to the Code of Conduct should be applied to the source TOML files in code_of_conduct/sections/ (specifically 1.toml and 2.toml) rather than editing the generated README.md directly. Since the repository uses a Jinja template to build the README, direct modifications will be lost during the next regeneration.
| Avoid spam, low-effort or “brainrot” messages (often abbreviated to LQ or low quality), incoherent text, animal sounds, disruptive speech, or otherwise obnoxious behavior. Contribute meaningfully and with substantial value. These are some common examples. | ||
| * Any sort of classic copy and paste brainrot, such as "erm what the sigma", or anyother late stage brainrot. |
There was a problem hiding this comment.
Use a colon to introduce the list of examples and fix the typo 'anyother' to 'any other'.
| Avoid spam, low-effort or “brainrot” messages (often abbreviated to LQ or low quality), incoherent text, animal sounds, disruptive speech, or otherwise obnoxious behavior. Contribute meaningfully and with substantial value. These are some common examples. | |
| * Any sort of classic copy and paste brainrot, such as "erm what the sigma", or anyother late stage brainrot. | |
| Avoid spam, low-effort or “brainrot” messages (often abbreviated to LQ or low quality), incoherent text, animal sounds, disruptive speech, or otherwise obnoxious behavior. Contribute meaningfully and with substantial value. These are some common examples: | |
| * Any sort of classic copy and paste brainrot, such as "erm what the sigma", or any other late stage brainrot. |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
README.md (1)
85-86: Optional: tighten the wording of the conspiracy theories prohibition.The surrounding sentences in this section use "Avoid …" and "Do not …" constructions, so "also prohibited" reads as slightly inconsistent. Consider aligning the phrasing:
✏️ Suggested rewording
-Conspiracy theories are also prohibited. +Promoting or spreading conspiracy theories is not permitted.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@README.md` around lines 85 - 86, The sentence "Conspiracy theories are also prohibited." is inconsistent with nearby "Avoid ..." and "Do not ..." phrasing; change it to match that imperative style (e.g., replace with "Do not promote or spread conspiracy theories.") and ensure surrounding lines preserve parallel structure and tone; update the README.md sentence accordingly.
📜 Review details
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
README.md
🧰 Additional context used
🪛 LanguageTool
README.md
[grammar] ~127-~127: Use a hyphen to join words.
Context: ...mon examples. * Any sort of classic copy and paste brainrot, such as "erm what th...
(QB_NEW_EN_HYPHEN)
[grammar] ~127-~127: Use a hyphen to join words.
Context: ...examples. * Any sort of classic copy and paste brainrot, such as "erm what the si...
(QB_NEW_EN_HYPHEN)
[grammar] ~128-~128: Use a hyphen to join words.
Context: ..., or anyother late stage brainrot. * Low thought single word message spam, like "...
(QB_NEW_EN_HYPHEN)
[grammar] ~128-~128: Use a hyphen to join words.
Context: ...ate stage brainrot. * Low thought single word message spam, like "guh" or "Chat!"...
(QB_NEW_EN_HYPHEN)
🔇 Additional comments (1)
README.md (1)
90-91: AI summary inconsistency: new bullet points and "Sensitive topics" subsection not reflected in annotations.The AI-generated summary states that "Ongoing global conflicts and war", "Sensitive historical topics", and the entire "Sensitive topics" subsection (lines 93–98) were added in this PR, but none of those lines carry change markers (
~) in the annotated diff. It is unclear whether these lines existed before this PR or were silently introduced. Please confirm whether lines 90–98 are genuinely unchanged or were part of this commit.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@README.md`:
- Around line 127-128: Update the two README bullet points: change "anyother" to
"any other", hyphenate the compound modifiers so "copy and paste brainrot"
becomes "copy-and-paste brainrot" and "late stage brainrot" becomes "late-stage
brainrot", and rewrite "Low thought single word message spam" as "Low-thought,
single-word message spam" (preserving the original meaning and punctuation).
---
Nitpick comments:
In `@README.md`:
- Around line 85-86: The sentence "Conspiracy theories are also prohibited." is
inconsistent with nearby "Avoid ..." and "Do not ..." phrasing; change it to
match that imperative style (e.g., replace with "Do not promote or spread
conspiracy theories.") and ensure surrounding lines preserve parallel structure
and tone; update the README.md sentence accordingly.
| * Any sort of classic copy and paste brainrot, such as "erm what the sigma", or anyother late stage brainrot. | ||
| * Low thought single word message spam, like "guh" or "Chat!". |
There was a problem hiding this comment.
Fix typo and compound-modifier hyphenation in bullet points.
Three issues on these two lines (static analysis also flags the hyphenation):
anyother→any other(missing space, line 127)copy and paste brainrot→copy-and-paste brainrot(compound adjective, line 127)late stage brainrot→late-stage brainrot(compound adjective, line 127)Low thought single word message spam→Low-thought, single-word message spam(compound adjectives, line 128)
✏️ Proposed fix
-* Any sort of classic copy and paste brainrot, such as "erm what the sigma", or anyother late stage brainrot.
-* Low thought single word message spam, like "guh" or "Chat!".
+* Any sort of classic copy-and-paste brainrot, such as "erm what the sigma", or any other late-stage brainrot.
+* Low-thought, single-word message spam, like "guh" or "Chat!".📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| * Any sort of classic copy and paste brainrot, such as "erm what the sigma", or anyother late stage brainrot. | |
| * Low thought single word message spam, like "guh" or "Chat!". | |
| * Any sort of classic copy-and-paste brainrot, such as "erm what the sigma", or any other late-stage brainrot. | |
| * Low-thought, single-word message spam, like "guh" or "Chat!". |
🧰 Tools
🪛 LanguageTool
[grammar] ~127-~127: Use a hyphen to join words.
Context: ...mon examples. * Any sort of classic copy and paste brainrot, such as "erm what th...
(QB_NEW_EN_HYPHEN)
[grammar] ~127-~127: Use a hyphen to join words.
Context: ...examples. * Any sort of classic copy and paste brainrot, such as "erm what the si...
(QB_NEW_EN_HYPHEN)
[grammar] ~128-~128: Use a hyphen to join words.
Context: ..., or anyother late stage brainrot. * Low thought single word message spam, like "...
(QB_NEW_EN_HYPHEN)
[grammar] ~128-~128: Use a hyphen to join words.
Context: ...ate stage brainrot. * Low thought single word message spam, like "guh" or "Chat!"...
(QB_NEW_EN_HYPHEN)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@README.md` around lines 127 - 128, Update the two README bullet points:
change "anyother" to "any other", hyphenate the compound modifiers so "copy and
paste brainrot" becomes "copy-and-paste brainrot" and "late stage brainrot"
becomes "late-stage brainrot", and rewrite "Low thought single word message
spam" as "Low-thought, single-word message spam" (preserving the original
meaning and punctuation).
1 participant
I made modifications to 1.2, 1.3 and the LQ message situation.