Repository navigation
docs: rename the community team to Clawkeepers - #21
Merged
Merged
Conversation
|
🦞👀 Pull request received. I will update this pull request when review starts. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What Problem This Solves
The community documentation still calls the team “Community Team” or “Community Staff” instead of its current name, Clawkeepers.
User Impact
Users and new Clawkeepers see consistent team naming across the guide, onboarding, Discord copy, and supporting references. Moderation policies, permissions, support routes, and repository URLs are unchanged.
Why This Change Was Made
Introduce the Clawkeepers as OpenClaw’s community team, use “Clawkeeper” for an individual member, and replace the former team names in the Krill guidance and archived bot reference.
Evidence
No remaining “Community Team” or “Community Staff” proper-name references in tracked text.
Relative Markdown links resolve, and
git diff --checkpasses.Discord copy remains below the 2,000-character limit at 1,953 UTF-16 code units.
Completed local ClawSweeper review: no actionable findings.