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

Update README.md #301

Merged
merged 1 commit into from
Apr 19, 2024
Merged

Update README.md #301

merged 1 commit into from
Apr 19, 2024

Conversation

zmanian
Copy link
Contributor

@zmanian zmanian commented Apr 18, 2024

Closes: #XXX

Description

@zmanian zmanian enabled auto-merge (squash) April 18, 2024 20:22
Copy link

coderabbitai bot commented Apr 18, 2024

Walkthrough

The update involves a simple change in the README file where the Telegram link has been updated. The previous link directed users to peggyvaults on Telegram, but it has now been changed to direct users to getsomm. This alteration suggests a shift in the communication or community management platform associated with the project.

Changes

File Change Summary
README.md Updated Telegram link from peggyvaults to getsomm.

Recent Review Details

Configuration used: CodeRabbit UI

Commits Files that changed from the base of the PR and between 01ad6c8 and d0830dd.
Files selected for processing (1)
  • README.md (1 hunks)
Additional Context Used
LanguageTool (21)
README.md (21)

Near line 1: Possible spelling mistake found.
Context: # Sommelier Sommelier is a platform for running De...


Near line 2: Possible spelling mistake found.
Context: # Sommelier Sommelier is a platform for running DeFi strategi...


Near line 9: Possible missing comma found.
Context: ...enable cross-chain execution. For more information you can check out the [Sommelier Docume...


Near line 9: Possible spelling mistake found.
Context: ...more information you can check out the [Sommelier Documentation](https://sommelier-financ...


Near line 25: Possible spelling mistake found.
Context: ... * Telegram ## Sommelier The initial release of the Sommelier b...


Near line 27: Possible spelling mistake found.
Context: ...# Sommelier The initial release of the Sommelier blockchain consists of a standard cosmo...


Near line 27: Possible spelling mistake found.
Context: ...elier blockchain consists of a standard cosmos-sdk chain and [Gravity Bridge refactor](htt...


Near line 35: Possible spelling mistake found.
Context: ... CLI that subsumes the functionality of gorc, and is used in this document to confi...


Near line 38: Possible spelling mistake found.
Context: ... and run the orchestrator. ## Join the mainnet! Running a validator node on the Somme...


Near line 40: Possible spelling mistake found.
Context: ...innet! Running a validator node on the Sommelier mainnet requires three processes: 1. T...


Near line 40: Possible spelling mistake found.
Context: ...nning a validator node on the Sommelier mainnet requires three processes: 1. The valid...


Near line 46: Possible spelling mistake found.
Context: ...peggyjv/steward) The Orchestrator (and Relayer if you are designated to run one) need ...


Near line 48: Possible spelling mistake found.
Context: ...mend using a service such as Alchemy or Infura. Larger validators may opt to use any e...


Near line 52: Consider removing “of” to be more concise
Context: ... reader. The Steward CLI now supports all of the same commands as gorc and is the reco...


Near line 52: Possible spelling mistake found.
Context: ...ow supports all of the same commands as gorc and is the recommended way to configur...


Near line 55: Possible missing comma found.
Context: ...st-installation steps for the steward process outlined at the end of the installation...


Near line 113: It appears that a comma is missing.
Context: ...val --chain-id sommelier-3 ``` At this point you need to create orchestrator keys OR...


Near line 144: Possible spelling mistake found.
Context: ...eaches upgrade block heights. The tool [cosmovisor](https://docs.cosmos.network/main/tooli...


Near line 192: It appears that a comma is missing.
Context: ...alidators.md) and return here. At this point you should have a server CA and server ...


Near line 193: Possible spelling mistake found.
Context: ...erver certificate for Steward, and your config.toml should be configured with those values...


Near line 206: Consider an alternative verb to strengthen your wording.
Context: ... Your installation is complete! If you have any problems, please reach out in the v...

Additional comments not posted (1)
README.md (1)

23-23: Update of Telegram link is correct and matches the PR objectives.


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:

Note: Auto-reply has been disabled for this repository by the repository owner. The CodeRabbit bot will not respond to your replies unless it is explicitly tagged.

  • 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @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.

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 as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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.

@zmanian zmanian disabled auto-merge April 18, 2024 20:22
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.

3 participants