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 #115

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dieinquicksand
Copy link

@dieinquicksand dieinquicksand commented Jun 3, 2024

Added Max Power as Advisor

Summary by CodeRabbit

  • Documentation
    • Updated the Readme.md file to include Max Power as a new advisor in the acknowledgments section.

Added Max Power as Advisor
Copy link

coderabbitai bot commented Jun 3, 2024

Walkthrough

The Readme.md file has been updated to include a new advisor, Max Power, in the acknowledgments section. This change replaces the previous mention of Grace Yu, who was listed as an external consultant. The update reflects a shift in the advisory team.

Changes

File Change Summary
Readme.md Added Max Power as an advisor, replacing Grace Yu who was listed as an external consultant.

Poem

A new advisor joins the scene,
Max Power's name now brightly gleams.
Grace Yu steps aside with grace,
To let Max Power take her place.
Our project grows, with strength anew,
With Max's wisdom guiding through.
🌟📘✨


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

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.

Copy link

@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 (10)
Readme.md (10)

Line range hint 27-27: Consider adding a comma before "and" in this complex sentence for better readability.

Tools
LanguageTool

[typographical] ~90-~90: This sign-off should end with a comma when followed by your name.
Context: ...l Consultant * Max Power - Advisor ## Thanks Notional would like to thank its deleg...

Markdownlint

84-84: Expected: 0 or 2; Actual: 1
Trailing spaces


89-89: Expected: 1; Actual: 2
Multiple consecutive blank lines


Line range hint 31-31: Consider using commas to enhance clarity in this long sentence.

Tools
LanguageTool

[typographical] ~90-~90: This sign-off should end with a comma when followed by your name.
Context: ...l Consultant * Max Power - Advisor ## Thanks Notional would like to thank its deleg...

Markdownlint

84-84: Expected: 0 or 2; Actual: 1
Trailing spaces


89-89: Expected: 1; Actual: 2
Multiple consecutive blank lines


Line range hint 39-39: Consider using a hyphen in "on-site bare metal" to form a compound adjective.

Tools
LanguageTool

[typographical] ~90-~90: This sign-off should end with a comma when followed by your name.
Context: ...l Consultant * Max Power - Advisor ## Thanks Notional would like to thank its deleg...

Markdownlint

84-84: Expected: 0 or 2; Actual: 1
Trailing spaces


89-89: Expected: 1; Actual: 2
Multiple consecutive blank lines


Line range hint 42-42: Consider replacing "At the present time" with "Currently" for conciseness.

Tools
LanguageTool

[typographical] ~90-~90: This sign-off should end with a comma when followed by your name.
Context: ...l Consultant * Max Power - Advisor ## Thanks Notional would like to thank its deleg...

Markdownlint

84-84: Expected: 0 or 2; Actual: 1
Trailing spaces


89-89: Expected: 1; Actual: 2
Multiple consecutive blank lines


Line range hint 45-45: Simplify "a variety of" to "various" for conciseness and add a comma after "project".

- a variety of services to any established or fledgling Cosmos project including:
+ various services to any established or fledgling Cosmos project, including:
Tools
LanguageTool

[typographical] ~90-~90: This sign-off should end with a comma when followed by your name.
Context: ...l Consultant * Max Power - Advisor ## Thanks Notional would like to thank its deleg...

Markdownlint

84-84: Expected: 0 or 2; Actual: 1
Trailing spaces


89-89: Expected: 1; Actual: 2
Multiple consecutive blank lines


90-90: Ensure the sign-off section ends with a comma.

Tools
LanguageTool

[typographical] ~90-~90: This sign-off should end with a comma when followed by your name.
Context: ...l Consultant * Max Power - Advisor ## Thanks Notional would like to thank its deleg...


Line range hint 17-17: Remove trailing spaces to adhere to Markdown best practices.

Also applies to: 56-56, 57-57, 77-77, 78-78, 80-80, 83-83, 84-84

Tools
LanguageTool

[typographical] ~90-~90: This sign-off should end with a comma when followed by your name.
Context: ...l Consultant * Max Power - Advisor ## Thanks Notional would like to thank its deleg...

Markdownlint

84-84: Expected: 0 or 2; Actual: 1
Trailing spaces


89-89: Expected: 1; Actual: 2
Multiple consecutive blank lines


89-89: Avoid multiple consecutive blank lines to maintain clean formatting.

Tools
Markdownlint

89-89: Expected: 1; Actual: 2
Multiple consecutive blank lines


Line range hint 17-17: Ensure headings are surrounded by blank lines for proper Markdown formatting.

Also applies to: 41-41, 44-44, 53-53

Tools
LanguageTool

[typographical] ~90-~90: This sign-off should end with a comma when followed by your name.
Context: ...l Consultant * Max Power - Advisor ## Thanks Notional would like to thank its deleg...

Markdownlint

84-84: Expected: 0 or 2; Actual: 1
Trailing spaces


89-89: Expected: 1; Actual: 2
Multiple consecutive blank lines


Line range hint 14-14: Add alternate text to the image for accessibility.

Tools
LanguageTool

[typographical] ~90-~90: This sign-off should end with a comma when followed by your name.
Context: ...l Consultant * Max Power - Advisor ## Thanks Notional would like to thank its deleg...

Markdownlint

84-84: Expected: 0 or 2; Actual: 1
Trailing spaces


89-89: Expected: 1; Actual: 2
Multiple consecutive blank lines

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between ead5d75 and 8c3ca38.

Files selected for processing (1)
  • Readme.md (1 hunks)
Additional context used
LanguageTool
Readme.md

[uncategorized] ~27-~27: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...re built on a philosophy of transparency and we are working towards building this in...


[style] ~31-~31: To make your text more readable, consider placing this phrase between commas.
Context: ...k. We want to contribute to systems that we believe will exist for decades and we need to m...


[uncategorized] ~31-~31: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...s that we believe will exist for decades and we need to make sure that these contrib...


[uncategorized] ~39-~39: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...ock rewards. We run exclusively on-site bare metal validators. The computers that run your...


[style] ~42-~42: ‘At the present time’ might be wordy. Consider a shorter alternative.
Context: ...IBC packets between Cosmos blockchains. At the present time, these relayers are not incentivized, b...


[style] ~45-~45: The phrase “a variety of” may be wordy. To make your writing clearer, consider replacing it.
Context: ...e developers is capable of contributing a variety of services to any established or fledglin...


[uncategorized] ~45-~45: Possible missing comma found.
Context: ... to any established or fledgling Cosmos project including: * Custom SDK Modules * CosmW...


[typographical] ~90-~90: This sign-off should end with a comma when followed by your name.
Context: ...l Consultant * Max Power - Advisor ## Thanks Notional would like to thank its deleg...

Markdownlint
Readme.md

17-17: Expected: 0 or 2; Actual: 1
Trailing spaces


56-56: Expected: 0 or 2; Actual: 1
Trailing spaces


57-57: Expected: 0 or 2; Actual: 1
Trailing spaces


77-77: Expected: 0 or 2; Actual: 1
Trailing spaces


78-78: Expected: 0 or 2; Actual: 1
Trailing spaces


80-80: Expected: 0 or 2; Actual: 1
Trailing spaces


83-83: Expected: 0 or 2; Actual: 1
Trailing spaces


84-84: Expected: 0 or 2; Actual: 1
Trailing spaces


89-89: Expected: 1; Actual: 2
Multiple consecutive blank lines


17-17: Expected: 1; Actual: 0; Below
Headings should be surrounded by blank lines


41-41: Expected: 1; Actual: 0; Below
Headings should be surrounded by blank lines


44-44: Expected: 1; Actual: 0; Below
Headings should be surrounded by blank lines


53-53: Expected: 1; Actual: 0; Below
Headings should be surrounded by blank lines


46-46: null
Lists should be surrounded by blank lines


14-14: null
Images should have alternate text (alt text)

Additional comments not posted (2)
Readme.md (2)

87-87: Update in the Team section is accurate and reflects the PR's objective.


Line range hint 46-46: Surround lists with blank lines for proper Markdown formatting.
[REFACTOR_SUGGESTion]

Tools
LanguageTool

[typographical] ~90-~90: This sign-off should end with a comma when followed by your name.
Context: ...l Consultant * Max Power - Advisor ## Thanks Notional would like to thank its deleg...

Markdownlint

84-84: Expected: 0 or 2; Actual: 1
Trailing spaces


89-89: Expected: 1; Actual: 2
Multiple consecutive blank lines

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.

1 participant