ci: update of files from global .github repo #186
Conversation
asyncapi-bot
requested review from
asyncapi-bot-eve,
gimlet2 and
lorenzsimon
as code owners
WalkthroughReplaces the existing Contributor Covenant with the Contributor Covenant 3.0 Code of Conduct, restructuring sections, updating language, adding an enforcement framework and expanded reporting guidance, clarifying scope, and updating attribution and resources. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
Pre-merge checks and finishing touches❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
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 |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
CODE_OF_CONDUCT.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
CODE_OF_CONDUCT.md
[style] ~31-~31: ‘on the basis of’ might be wordy. Consider a shorter alternative.
Context: ...rizing anyone’s personality or behavior on the basis of immutable identities or traits. 4. **Se...
(EN_WORDINESS_PREMIUM_ON_THE_BASIS_OF)
[grammar] ~39-~39: There might be a mistake here.
Context: ...meone else to evade enforcement actions. 2. Failing to credit sources. Not properl...
(QB_NEW_EN)
[style] ~53-~53: In some texts, you can shorten this phrase. Consider using “email us”.
Context: ...f_conduct). - Or, if you’d prefer, just send us an email at [email protected]. Community...
(SEND_PRP_AN_EMAIL)
[style] ~55-~55: Consider a more concise word here.
Context: ...rioritizing safety and confidentiality. In order to honor these values, enforcement actions...
(IN_ORDER_TO_PREMIUM)
[grammar] ~66-~66: There might be a mistake here.
Context: ...n warning from the Community Moderators. 3) Repair: Examples of repair include a pri...
(QB_NEW_EN)
[grammar] ~72-~72: There might be a mistake here.
Context: ... period is over. 3) Temporary Suspension 1) Event: A pattern of repeated violation w...
(QB_NEW_EN)
[grammar] ~73-~73: There might be a mistake here.
Context: ...warnings, or a single serious violation. 2) Consequence: A private written warning w...
(QB_NEW_EN)
[grammar] ~76-~76: There might be a mistake here.
Context: ...e suspension is lifted. 4) Permanent Ban 1) Event: A pattern of repeated code of con...
(QB_NEW_EN)
[grammar] ~77-~77: There might be a mistake here.
Context: ...unity safe with this person as a member. 2) Consequence: Access to all community spa...
(QB_NEW_EN)
[style] ~81-~81: ‘in keeping with’ might be wordy. Consider a shorter alternative.
Context: ...s to use their discretion and judgment, in keeping with the best interests of our community. ...
(EN_WORDINESS_PREMIUM_IN_KEEPING_WITH)
🪛 markdownlint-cli2 (0.18.1)
CODE_OF_CONDUCT.md
53-53: Bare URL used
(MD034, no-bare-urls)
| Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [email protected]. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately. | ||
| ## Addressing and Repairing Harm | ||
|
|
||
| **** |
There was a problem hiding this comment.
Remove the stray formatting marker.
The lone **** renders as empty bold text in Markdown and looks like a leftover placeholder. Please drop it or replace it with an intentional separator (for example, ---) if a divider is desired.
🤖 Prompt for AI Agents
In CODE_OF_CONDUCT.md around line 60 there is a stray "****" markdown sequence
that renders as empty bold text; remove that sequence or replace it with an
intentional separator such as "---" (or a meaningful heading/divider) so the
file no longer contains the leftover formatting marker and the document renders
correctly.
| 2) Consequence: Access to all community spaces, tools, and communication channels is removed. In general, permanent bans should be rarely used, should have strong reasoning behind them, and should only be resorted to if working through other remedies has failed to change the behavior. | ||
| 3) Repair: There is no possible repair in cases of this severity. | ||
|
|
||
| This enforcement ladder is intended as a guideline. It does not limit the ability of Community Managers to use their discretion and judgment, in keeping with the best interests of our community. |
There was a problem hiding this comment.
Align the enforcement role naming.
Earlier sections refer to “Community Moderators,” but this sentence switches to “Community Managers.” That mismatch can create confusion about who is responsible for enforcement. Please stick to one term (whichever is correct for AsyncAPI) throughout the document.
🧰 Tools
🪛 LanguageTool
[style] ~81-~81: ‘in keeping with’ might be wordy. Consider a shorter alternative.
Context: ...s to use their discretion and judgment, in keeping with the best interests of our community. ...
(EN_WORDINESS_PREMIUM_IN_KEEPING_WITH)
🤖 Prompt for AI Agents
In CODE_OF_CONDUCT.md around line 81, the sentence uses "Community Managers"
while earlier sections use "Community Moderators"; update this sentence to use
the consistent term "Community Moderators" (or the authoritative AsyncAPI term
if different) and scan the document for any other mismatched occurrences to make
all enforcement-role names identical; ensure capitalization matches the chosen
term throughout.
2 participants
Summary by CodeRabbit