Update README.md

[JulienMassonnat]

I need a new push to redeploy the main branch on vercel (instead of staging)

Summary by CodeRabbit

• Documentation
  • Updated wording in the README.md for improved clarity and consistency.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
docs	🔄 Building (Inspect)	Visit Preview	💬 Add feedback	Jul 22, 2024 9:39am

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The recent change to the Axone documentation repository involves a minor textual update in the README.md file, transforming the phrase "powered ❤️ by" to "powered with ❤️ by." This adjustment is purely cosmetic, enhancing the clarity of the expression without altering the meaning or impacting any functionality within the documentation.

Changes

File	Change Summary
README.md	Changed "powered ❤️ by" to "powered with ❤️ by"

Poem

🐰 In the land of code and cheer,
A small change brings us near,
"Powered with ❤️" now shines bright,
A cozy tweak, a joyful sight!
Hopping on through lines of text,
Our documentation now is blessed!
🌟

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[bot-anik]

🙋‍ Oops! This branch name does not follow the naming convention.

---

Please, see the following branch naming convention: Branch naming convention | Purpose ------------------------ | ------- `feat/**` | A new feature `fix/**` | A bug fix `build/**` | Changes that affect the build system (npm, mavem, poetry) `ci/**` | Changes to the CI configuration `docs/**` | Documentation only changes `style/**` | Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc) `refactor/**` | Code changes that neither fixe a bug nor adds a feature `perf/**` | Code changes that improve performance `test/**` | When adding tests or correcting existing tests `chore/**` | Other changes that don't modify source

[bot-anik]

🙅 Closing the PR because it does not respect naming conventions. Edit the branch name and submit a new PR.

[bot-anik]

Device	URL
desktop	http://localhost:3000/

Device	URL
mobile	http://localhost:3000/

Not what you expected? Are your scores flaky? GitHub runners could be the cause.
Try running on Foo instead