Skip to content

Add guide: Migrate your group and update its details#10

Draft
shrn-werk wants to merge 4 commits into
gitbookfrom
claude/tender-shannon-GJ38S
Draft

Add guide: Migrate your group and update its details#10
shrn-werk wants to merge 4 commits into
gitbookfrom
claude/tender-shannon-GJ38S

Conversation

@shrn-werk

@shrn-werk shrn-werk commented May 26, 2026

Copy link
Copy Markdown
Contributor

Summary

Adds a new guide for group admins on how to migrate their group and fill in the new group contract properties via the admin app.

  • New page: docs/circles-sdk/circles-avatars/group-avatars/migrate-group-and-update-details.md
  • Linked in SUMMARY.md under Group Avatars

Adds a step-by-step guide for group admins covering how to add their
Circles profile as a signer on the owner Safe and how to fill in the
new group contract properties via the admin app.

https://claude.ai/code/session_01Dzge154ZrxRskefrJU726b
@coderabbitai

coderabbitai Bot commented May 26, 2026

Copy link
Copy Markdown

Walkthrough

This pull request adds a new migration guide for group avatars and registers it in the documentation table of contents. The guide walks group admins through two parts: making their Circles profile a signer of the group owner Safe via the Safe UI, and updating group details (description, type, contact info, fee criteria) in the admin app.

Changes

Group Avatar Migration Guide

Layer / File(s) Summary
TOC entry and document front-matter
docs/SUMMARY.md, docs/circles-sdk/circles-avatars/group-avatars/migrate-group-and-update-details.md
New table-of-contents entry registered under Group Avatars; document metadata and icon established.
Introduction and prerequisites
docs/circles-sdk/circles-avatars/group-avatars/migrate-group-and-update-details.md
Document introduces the end-to-end migration process and outlines assumptions about group creation context and which instructional steps apply.
Part 1: Safe owner signer workflow
docs/circles-sdk/circles-avatars/group-avatars/migrate-group-and-update-details.md
Step-by-step instructions for locating the group's owner Safe, connecting as the Safe owner, retrieving the admin's Circles profile address, adding it as a signer, and confirming the authorisation.
Part 2: Admin app group details update
docs/circles-sdk/circles-avatars/group-avatars/migrate-group-and-update-details.md
Step-by-step instructions for signing into the admin app, opening the group, editing new fields (description, group type, contact details, optional fee and criteria), and saving the changes.
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately summarises the main change: adding a guide for migrating groups and updating their details, which matches the new documentation page and SUMMARY.md link.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Description check ✅ Passed The pull request description accurately describes the changeset, including new documentation page and summary update.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch claude/tender-shannon-GJ38S

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.

@shrn-werk
shrn-werk marked this pull request as ready for review May 26, 2026 15:15
@shrn-werk
shrn-werk marked this pull request as draft May 26, 2026 15:15

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (2)
docs/circles-sdk/circles-avatars/group-avatars/migrate-group-and-update-details.md (2)

43-43: 💤 Low value

Consider defining or linking the EOA acronym.

The term "owner EOA" is used without definition. Whilst "EOA" (Externally-Owned Account) may be familiar to blockchain developers, consider either defining it inline or linking to the glossary for clarity, especially since this guide targets group admins who may not be deeply technical.

✏️ Suggested clarification
-Connect to the Safe UI using your owner EOA — the wallet that owns the Safe.
+Connect to the Safe UI using your owner EOA (externally-owned account) — the wallet that owns the Safe.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In
`@docs/circles-sdk/circles-avatars/group-avatars/migrate-group-and-update-details.md`
at line 43, The phrase "owner EOA" used in the sentence "Connect to the Safe UI
using your owner EOA — the wallet that owns the Safe." is undefined; update the
sentence to either expand EOA to "Externally-Owned Account (EOA)" on first
mention or add a hyperlink to the glossary/definition, ensuring the phrase
"owner EOA" is clearly described for non-technical readers so they understand it
refers to the wallet that holds the Safe's ownership.

1-6: 💤 Low value

Check icon choice for intended consistencymigrate-group-and-update-details.md uses icon: user-gear while group-avatars/README.md uses icon: users-medical; however other pages in the same group-avatars directory also use different icons (e.g., people-group), so this may be intentional—confirm the design intent.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In
`@docs/circles-sdk/circles-avatars/group-avatars/migrate-group-and-update-details.md`
around lines 1 - 6, Confirm the intended icon for the group-avatars section,
then update the frontmatter in migrate-group-and-update-details.md to use the
chosen icon value consistently (replace icon: user-gear with the agreed icon,
e.g., users-medical or people-group) so it matches other pages in the directory;
if the variation is intentional, add a brief comment in the file or a note in
the directory README stating why migrate-group-and-update-details.md uses a
different icon.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In
`@docs/circles-sdk/circles-avatars/group-avatars/migrate-group-and-update-details.md`:
- Line 14: The document drops from an H1 to a level-3 heading; change the
heading level for "Assumptions" from "### Assumptions" to "## Assumptions" (and
likewise convert any other level-3 headings immediately following the top-level
title to level-2) so headings increment by one level only and restore proper
document structure.

---

Nitpick comments:
In
`@docs/circles-sdk/circles-avatars/group-avatars/migrate-group-and-update-details.md`:
- Line 43: The phrase "owner EOA" used in the sentence "Connect to the Safe UI
using your owner EOA — the wallet that owns the Safe." is undefined; update the
sentence to either expand EOA to "Externally-Owned Account (EOA)" on first
mention or add a hyperlink to the glossary/definition, ensuring the phrase
"owner EOA" is clearly described for non-technical readers so they understand it
refers to the wallet that holds the Safe's ownership.
- Around line 1-6: Confirm the intended icon for the group-avatars section, then
update the frontmatter in migrate-group-and-update-details.md to use the chosen
icon value consistently (replace icon: user-gear with the agreed icon, e.g.,
users-medical or people-group) so it matches other pages in the directory; if
the variation is intentional, add a brief comment in the file or a note in the
directory README stating why migrate-group-and-update-details.md uses a
different icon.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 04f8d688-22e5-4c82-b589-78bca61babae

📥 Commits

Reviewing files that changed from the base of the PR and between af4dde4 and 232086a.

📒 Files selected for processing (2)
  • docs/SUMMARY.md
  • docs/circles-sdk/circles-avatars/group-avatars/migrate-group-and-update-details.md


The process is straightforward: you add your Circles profile as a signer of the group's owner Safe, then use that connection to edit the group in the admin app.

### Assumptions

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Fix heading level structure.

The document jumps from a level-1 heading (line 8) to a level-3 heading here, skipping level 2. Markdown best practice requires headings to increment by only one level at a time for proper document structure, accessibility, and navigation.

📝 Proposed fix

Change the level-3 headings to level-2:

-### Assumptions
+## Assumptions

Apply the same change to line 22:

-### Which steps apply to you?
+## Which steps apply to you?
📝 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.

Suggested change
### Assumptions
## Assumptions
🧰 Tools
🪛 markdownlint-cli2 (0.22.1)

[warning] 14-14: Heading levels should only increment by one level at a time
Expected: h2; Actual: h3

(MD001, heading-increment)

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In
`@docs/circles-sdk/circles-avatars/group-avatars/migrate-group-and-update-details.md`
at line 14, The document drops from an H1 to a level-3 heading; change the
heading level for "Assumptions" from "### Assumptions" to "## Assumptions" (and
likewise convert any other level-3 headings immediately following the top-level
title to level-2) so headings increment by one level only and restore proper
document structure.

shrn-werk and others added 3 commits May 26, 2026 17:20
Adds figure tags for the Group Checker owner-Safe screenshot (Step 2)
and the Circles profile wallet address screenshot (Step 4), and
removes the leftover TODO placeholder for Step 7.

https://claude.ai/code/session_01Dzge154ZrxRskefrJU726b
Relocates the guide from circles-sdk/circles-avatars/group-avatars/
to user-guides/circles-groups/, positioned between Create a Circles
Group and Technical Group Details. Updates image paths and adds a
User Guides section to SUMMARY.md.

https://claude.ai/code/session_01Dzge154ZrxRskefrJU726b
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