Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs(x/accounts): init of the x/accounts module docs. #22099

Merged
merged 5 commits into from
Oct 8, 2024

Conversation

testinginprod
Copy link
Contributor

@testinginprod testinginprod commented Oct 3, 2024

Description

Closes: #XXXX


Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

  • included the correct type prefix in the PR title, you can find examples of the prefixes below:
  • confirmed ! in the type prefix if API or client breaking change
  • targeted the correct branch (see PR Targeting)
  • provided a link to the relevant issue or specification
  • reviewed "Files changed" and left comments if necessary
  • included the necessary unit and integration tests
  • added a changelog entry to CHANGELOG.md
  • updated the relevant documentation or specification, including comments for documenting Go code
  • confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

Please see Pull Request Reviewer section in the contributing guide for more information on how to review a pull request.

I have...

  • confirmed the correct type prefix in the PR title
  • confirmed all author checklist items have been addressed
  • reviewed state machine logic, API design and naming, documentation is accurate, tests and test coverage

Summary by CodeRabbit

  • Documentation
    • Enhanced documentation for the x/accounts module, improving clarity and structure.
    • Added detailed sections on account creation, including account structs and initialization messages.
    • Introduced the Authentication interface, emphasizing sender verification and security.
    • Expanded guidance on custom accounts in the x/auth gRPC server and genesis account creation process.

Copy link
Contributor

coderabbitai bot commented Oct 3, 2024

Caution

Review failed

The pull request is closed.

📝 Walkthrough
📝 Walkthrough

Walkthrough

The pull request introduces extensive enhancements to the documentation of the x/accounts module within the Cosmos SDK. It provides a detailed overview of advanced smart accounts, including their structure, functionality, and the processes for account creation and management. Key additions include new messages and methods relevant to account operations, as well as an introduction to the Authentication interface, which supports flexible transaction authentication. The documentation also covers the integration of custom accounts with the x/auth gRPC server and outlines the genesis account creation process.

Changes

File Change Summary
x/accounts/README.md - Added comprehensive documentation on advanced smart accounts, including account basics and handlers.
- Introduced new messages: MsgInit, MsgInitResponse, MsgIncreaseCounter, MsgIncreaseCounterResponse, QueryCounter, QueryCounterResponse.
- Added new methods: Authenticate, AuthRetroCompatibility, and NewAccount.

Possibly related PRs

Suggested reviewers

  • sontrinh16
  • tac0turtle
  • akhilkumarpilli

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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.
    • Generate unit testing code for this file.
    • 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. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • 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 src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

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.

Documentation and Community

  • 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.

@testinginprod testinginprod marked this pull request as ready for review October 4, 2024 10:56
@testinginprod testinginprod requested review from sontrinh16 and a team as code owners October 4, 2024 10:56
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

🧹 Outside diff range and nitpick comments (8)
x/accounts/README.md (8)

Line range hint 1-17: Improve document structure and formatting

The introduction and basics sections provide a good overview of the x/accounts module. However, there are some formatting inconsistencies that should be addressed:

  1. The main title should be the only H1 (#) in the document. Consider changing "Basics" to an H2 (##).
  2. Use consistent list formatting. Currently, some lists use dashes (-) while others use numbers. Stick to one style for unordered lists (preferably asterisks *) and use numbers for ordered lists.

Additionally, consider adding a table of contents at the beginning of the document to improve navigation.

🧰 Tools
🪛 LanguageTool

[uncategorized] ~254-~254: Loose punctuation mark.
Context: ...essential components: 1. AddressCodec: For encoding and decoding addresses 2. ...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~322-~322: Loose punctuation mark.
Context: ...s. Key functions include: 1. Whoami(): Retrieves the address of the current ac...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~323-~323: Loose punctuation mark.
Context: ...ss of the current account. 2. Sender(): Gets the address of the transaction sen...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~324-~324: Loose punctuation mark.
Context: ...(not available in queries). 3. Funds(): Retrieves funds provided by the sender ...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~325-~325: Loose punctuation mark.
Context: ...ing Init or Execution. 4. ExecModule(): Allows the account to execute a module ...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~327-~327: Loose punctuation mark.
Context: ... on behalf of others. 5. QueryModule(): Enables querying a module. These funct...

(UNLIKELY_OPENING_PUNCTUATION)


[grammar] ~339-~339: Possible subject-verb agreement error detected.
Context: ...on sets of messages and/or queries that accounts can handle. Example: Transaction Authe...

(PLURAL_THAT_AGREEMENT)

🪛 Markdownlint

37-37: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


38-38: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


54-54: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


55-55: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


109-109: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


110-110: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


179-179: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


180-180: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


343-343: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


344-344: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


345-345: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


199-199: Expected: 1; Actual: 2; Style: 1/1/1
Ordered list item prefix

(MD029, ol-prefix)


19-224: Enhance clarity and code formatting in the account creation section

The account creation section is comprehensive and informative. To further improve it:

  1. Add language identifiers to code blocks for proper syntax highlighting. For example, use go for Go code and protobuf for Protobuf definitions.
  2. Consider breaking down the large "Example account creation" section into smaller subsections with clear H3 (###) headers for each major step (e.g., "Defining Account State", "Implementing Init Method", "Adding Execute Handlers", "Adding Query Handlers").
  3. In the "State Isolation" explanation, consider using a code example to illustrate how two accounts of the same type maintain separate states.

These changes will enhance readability and make it easier for developers to follow the account creation process.

🧰 Tools
🪛 Markdownlint

37-37: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


38-38: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


54-54: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


55-55: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


109-109: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


110-110: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


179-179: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


180-180: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


199-199: Expected: 1; Actual: 2; Style: 1/1/1
Ordered list item prefix

(MD029, ol-prefix)


225-316: Enhance the app wiring section structure and context

The app wiring section provides valuable information on integrating the created account with the x/accounts module. To improve this section:

  1. Add a brief introduction explaining the purpose of app wiring and why it's necessary.
  2. Use H3 (###) headers for the "Depinject Method" and "Manual Method" subsections for better structure.
  3. Consider adding a brief comparison of the two methods, highlighting when to use each approach.
  4. In the Manual Method example, add a comment explaining what accountstd.AddAccount does and why it's used.

These changes will provide more context and help developers choose the appropriate wiring method for their application.

🧰 Tools
🪛 LanguageTool

[uncategorized] ~254-~254: Loose punctuation mark.
Context: ...essential components: 1. AddressCodec: For encoding and decoding addresses 2. ...

(UNLIKELY_OPENING_PUNCTUATION)


317-330: Improve structure and add examples in the accountsstd package section

The accountsstd package section provides useful information about utility functions. To enhance this section:

  1. Consider using a bulleted list for the key functions instead of numbered list for consistency with other sections.
  2. Add brief code examples for each key function to illustrate their usage.
  3. Include a note on error handling when using these functions.
  4. Mention any limitations or considerations when using these utility functions.

These additions will make the section more practical and help developers understand how to use the accountsstd package effectively.

🧰 Tools
🪛 LanguageTool

[uncategorized] ~322-~322: Loose punctuation mark.
Context: ...s. Key functions include: 1. Whoami(): Retrieves the address of the current ac...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~323-~323: Loose punctuation mark.
Context: ...ss of the current account. 2. Sender(): Gets the address of the transaction sen...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~324-~324: Loose punctuation mark.
Context: ...(not available in queries). 3. Funds(): Retrieves funds provided by the sender ...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~325-~325: Loose punctuation mark.
Context: ...ing Init or Execution. 4. ExecModule(): Allows the account to execute a module ...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~327-~327: Loose punctuation mark.
Context: ... on behalf of others. 5. QueryModule(): Enables querying a module. These funct...

(UNLIKELY_OPENING_PUNCTUATION)


331-351: Expand on interfaces via messages and queries

The section on interfaces via messages and queries introduces an important concept. To make it more comprehensive:

  1. Provide a more detailed example of how different account types can implement the same interface.
  2. Explain the benefits of using this approach for interface definition (e.g., flexibility, extensibility).
  3. Consider adding a simple code example showing how to define and implement an interface using messages and queries.
  4. Mention any best practices or considerations when designing interfaces this way.

These additions will help developers better understand and utilize the interface concept in the x/accounts module.

🧰 Tools
🪛 LanguageTool

[grammar] ~339-~339: Possible subject-verb agreement error detected.
Context: ...on sets of messages and/or queries that accounts can handle. Example: Transaction Authe...

(PLURAL_THAT_AGREEMENT)

🪛 Markdownlint

343-343: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


344-344: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


345-345: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


Line range hint 352-443: Enhance clarity in the authentication interface section

The authentication interface section is comprehensive and well-structured. To further improve it:

  1. In the sequence diagram, consider adding a brief explanation of each step to make it more accessible to readers who might not be familiar with sequence diagrams.
  2. In the code example, add comments explaining the purpose of each method and any important considerations (e.g., why sender verification is crucial).
  3. Expand on the "Key Implementation Points" section, providing more details on how to prevent replay attacks and ensure authentication safety.
  4. Consider adding a subsection on best practices for implementing the Authentication interface.

These enhancements will provide developers with a more thorough understanding of the Authentication interface and its implementation.

🧰 Tools
🪛 LanguageTool

[uncategorized] ~254-~254: Loose punctuation mark.
Context: ...essential components: 1. AddressCodec: For encoding and decoding addresses 2. ...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~322-~322: Loose punctuation mark.
Context: ...s. Key functions include: 1. Whoami(): Retrieves the address of the current ac...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~323-~323: Loose punctuation mark.
Context: ...ss of the current account. 2. Sender(): Gets the address of the transaction sen...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~324-~324: Loose punctuation mark.
Context: ...(not available in queries). 3. Funds(): Retrieves funds provided by the sender ...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~325-~325: Loose punctuation mark.
Context: ...ing Init or Execution. 4. ExecModule(): Allows the account to execute a module ...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~327-~327: Loose punctuation mark.
Context: ... on behalf of others. 5. QueryModule(): Enables querying a module. These funct...

(UNLIKELY_OPENING_PUNCTUATION)


[grammar] ~339-~339: Possible subject-verb agreement error detected.
Context: ...on sets of messages and/or queries that accounts can handle. Example: Transaction Authe...

(PLURAL_THAT_AGREEMENT)

🪛 Markdownlint

37-37: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


38-38: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


54-54: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


55-55: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


109-109: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


110-110: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


179-179: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


180-180: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


343-343: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


344-344: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


345-345: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


199-199: Expected: 1; Actual: 2; Style: 1/1/1
Ordered list item prefix

(MD029, ol-prefix)


Line range hint 496-534: Expand the genesis section with more context and examples

The genesis section provides valuable information on creating accounts at genesis. To enhance this section:

  1. Add a brief introduction explaining the importance of genesis account creation and when it might be necessary.
  2. Provide more context around the simd accounts tx init command, including what simd is and where to find more information about it.
  3. Expand on the explanation of the genesis.json file structure, particularly the init_account_msgs field.
  4. Consider adding an example of how to verify that the genesis accounts were created successfully after chain initialization.

These additions will provide a more comprehensive guide to creating accounts at genesis, helping developers understand both the process and its implications.


Line range hint 1-534: Resolve markdown formatting inconsistencies

To improve the overall consistency and readability of the document, please address the following markdown formatting issues:

  1. Use consistent list item markers throughout the document. Prefer asterisks (*) for unordered lists and numbers for ordered lists.
  2. Ensure proper indentation for nested lists to improve readability.
  3. Use consistent heading levels. Main sections should use H2 (##), subsections should use H3 (###), and so on.
  4. Add a single space after list item markers and heading symbols for better rendering.

Resolving these formatting issues will enhance the document's overall appearance and make it easier to read and maintain.

🧰 Tools
🪛 LanguageTool

[uncategorized] ~254-~254: Loose punctuation mark.
Context: ...essential components: 1. AddressCodec: For encoding and decoding addresses 2. ...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~322-~322: Loose punctuation mark.
Context: ...s. Key functions include: 1. Whoami(): Retrieves the address of the current ac...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~323-~323: Loose punctuation mark.
Context: ...ss of the current account. 2. Sender(): Gets the address of the transaction sen...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~324-~324: Loose punctuation mark.
Context: ...(not available in queries). 3. Funds(): Retrieves funds provided by the sender ...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~325-~325: Loose punctuation mark.
Context: ...ing Init or Execution. 4. ExecModule(): Allows the account to execute a module ...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~327-~327: Loose punctuation mark.
Context: ... on behalf of others. 5. QueryModule(): Enables querying a module. These funct...

(UNLIKELY_OPENING_PUNCTUATION)


[grammar] ~339-~339: Possible subject-verb agreement error detected.
Context: ...on sets of messages and/or queries that accounts can handle. Example: Transaction Authe...

(PLURAL_THAT_AGREEMENT)

🪛 Markdownlint

37-37: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


38-38: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


54-54: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


55-55: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


109-109: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


110-110: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


179-179: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


180-180: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


343-343: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


344-344: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


345-345: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


199-199: Expected: 1; Actual: 2; Style: 1/1/1
Ordered list item prefix

(MD029, ol-prefix)

📜 Review details

Configuration used: .coderabbit.yml
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 8bbf51c and 8fb860a.

📒 Files selected for processing (1)
  • x/accounts/README.md (4 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
x/accounts/README.md (1)

Pattern **/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness"

🪛 LanguageTool
x/accounts/README.md

[uncategorized] ~254-~254: Loose punctuation mark.
Context: ...essential components: 1. AddressCodec: For encoding and decoding addresses 2. ...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~322-~322: Loose punctuation mark.
Context: ...s. Key functions include: 1. Whoami(): Retrieves the address of the current ac...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~323-~323: Loose punctuation mark.
Context: ...ss of the current account. 2. Sender(): Gets the address of the transaction sen...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~324-~324: Loose punctuation mark.
Context: ...(not available in queries). 3. Funds(): Retrieves funds provided by the sender ...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~325-~325: Loose punctuation mark.
Context: ...ing Init or Execution. 4. ExecModule(): Allows the account to execute a module ...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~327-~327: Loose punctuation mark.
Context: ... on behalf of others. 5. QueryModule(): Enables querying a module. These funct...

(UNLIKELY_OPENING_PUNCTUATION)


[grammar] ~339-~339: Possible subject-verb agreement error detected.
Context: ...on sets of messages and/or queries that accounts can handle. Example: Transaction Authe...

(PLURAL_THAT_AGREEMENT)

🪛 Markdownlint
x/accounts/README.md

37-37: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


38-38: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


54-54: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


55-55: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


109-109: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


110-110: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


179-179: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


180-180: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


343-343: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


344-344: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


345-345: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


199-199: Expected: 1; Actual: 2; Style: 1/1/1
Ordered list item prefix

(MD029, ol-prefix)


494-494: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


495-495: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)

@@ -2,6 +2,354 @@

The x/accounts module enhances the Cosmos SDK by providing tools and infrastructure for creating advanced smart accounts.

# Basics
Copy link
Member

Choose a reason for hiding this comment

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

could you increment all the headers? You shouldn't have multiple titles in the document

Copy link
Member

@tac0turtle tac0turtle left a comment

Choose a reason for hiding this comment

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

LGTM, it would be good to get an example on how to work through cosmwasm with accounts

@julienrbrt julienrbrt mentioned this pull request Oct 7, 2024
4 tasks
@testinginprod testinginprod added this pull request to the merge queue Oct 8, 2024
Merged via the queue into main with commit 5fea67d Oct 8, 2024
69 checks passed
@testinginprod testinginprod deleted the tip/accounts/docs branch October 8, 2024 13:38
@julienrbrt julienrbrt added the backport/v0.52.x PR scheduled for inclusion in the v0.52's next stable release label Oct 8, 2024
mergify bot pushed a commit that referenced this pull request Oct 8, 2024
julienrbrt pushed a commit that referenced this pull request Oct 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport/v0.52.x PR scheduled for inclusion in the v0.52's next stable release C:x/accounts
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants