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: Update slashing docs #22107

Merged
merged 2 commits into from
Oct 3, 2024
Merged

docs: Update slashing docs #22107

merged 2 commits into from
Oct 3, 2024

Conversation

lucaslopezf
Copy link
Contributor

@lucaslopezf lucaslopezf commented Oct 3, 2024

Description

ref: #21429


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

  • New Features

    • Introduced the update-params-proposal command for submitting governance proposals related to slashing module parameters.
  • Documentation

    • Updated the README.md with an example of the new command and revised references to protobuf files to a specific Cosmos SDK version.

Copy link
Contributor

coderabbitai bot commented Oct 3, 2024

📝 Walkthrough

Walkthrough

The changes involve updates to the README.md file for the x/slashing module in the Cosmos SDK. A new CLI command, update-params-proposal, has been added to enable users to submit governance proposals for slashing module parameter updates. Additionally, references to protobuf files have been updated to point to a specific version of the Cosmos SDK, ensuring accuracy. The overall structure of the document remains largely unchanged.

Changes

File Change Summary
x/slashing/README.md - Added new CLI command update-params-proposal for governance proposals.
- Updated protobuf file references to version v0.52.0-beta.1.

Possibly related PRs

  • docs: update authz docs #22062: This PR updates the x/authz/README.md file, adding a new command revoke-all in the CLI section, which is similar to the addition of the update-params-proposal command in the main PR for the x/slashing module. Both PRs enhance CLI functionality by introducing new commands.

Suggested reviewers

  • tac0turtle
  • sontrinh16

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.

@lucaslopezf lucaslopezf marked this pull request as ready for review October 3, 2024 15:26
Copy link
Member

@julienrbrt julienrbrt left a comment

Choose a reason for hiding this comment

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

lgtm!

@julienrbrt julienrbrt added the backport/v0.52.x PR scheduled for inclusion in the v0.52's next stable release label Oct 3, 2024
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 (3)
x/slashing/README.md (3)

146-146: Consider using a stable release version in the protobuf reference URL.

The protobuf reference URL has been updated to point to a specific beta version (v0.52.0-beta.1). While this is good for consistency, linking to a beta version might not be ideal for long-term stability of the documentation. Consider using a stable release version instead.


157-157: Consider using a stable release version in the protobuf reference URL.

The protobuf reference URL has been updated to point to a specific beta version (v0.52.0-beta.1). While this is good for consistency, linking to a beta version might not be ideal for long-term stability of the documentation. Consider using a stable release version instead.


637-649: Excellent addition of the update-params-proposal command.

The new update-params-proposal command is a valuable addition to the CLI section, allowing users to submit governance proposals for updating slashing module parameters. The example provided is clear and helpful.

To further improve this section, consider adding a brief explanation of what happens after the proposal is submitted. For instance, mention that it goes through the standard governance process, including voting, and if approved, the parameters will be updated.

📜 Review details

Configuration used: .coderabbit.yml
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between cd2c8ea and 7b5a354.

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

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

@julienrbrt julienrbrt added this pull request to the merge queue Oct 3, 2024
Merged via the queue into main with commit dda9679 Oct 3, 2024
72 checks passed
@julienrbrt julienrbrt deleted the lucas/slashing-docs branch October 3, 2024 17:06
mergify bot pushed a commit that referenced this pull request Oct 3, 2024
(cherry picked from commit dda9679)
@coderabbitai coderabbitai bot mentioned this pull request Oct 14, 2024
12 tasks
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/slashing
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants