Sponsors section is added.

[cinar]

Describe Request

Sponsors section is added.

Change Type

Document update.

Summary by CodeRabbit

• Documentation
  • Comprehensive updates to the README.md to reflect version 2 features and enhancements.
  • Added a new section titled "Our Sponsors" to acknowledge community support.
  • Clarified licensing information for versions 1.x.x and 2.x.x and above.

[coderabbitai]

Walkthrough

The pull request updates the README.md file to include a new section titled "Our Sponsors," which acknowledges community support and encourages sponsorship. It clarifies licensing information, specifying that versions 2.x.x and above are dual-licensed under the GNU AGPLv3 License and a commercial license, while version 1.x.x remains under the MIT License. The overall structure of the document, including sections on indicators, strategies, repositories, backtesting, usage instructions, and contribution guidelines, has been maintained.

Changes

File	Change Summary
README.md	- Added "Our Sponsors" section.
	- Updated licensing information for versions 2.x.x and 1.x.x.

Possibly related PRs

• Indicator logo is added. #240: The changes in this PR also involve updates to the README.md file, including clarifications on licensing information, which directly relates to the updates made in the main PR regarding license specifications.

🐇 "In the meadow, changes bloom,
With sponsors' names, we make room.
A codebase fresh, a license clear,
In Go we trust, our path is near.
With channels swift and tests so bright,
Version two hops into the light!" 🌼

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between bf25120 and 05dfe28.

📒 Files selected for processing (1)

• README.md (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• README.md

---

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

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.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 93.51%. Comparing base (7a4b44b) to head (05dfe28).

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #244   +/-   ##
=======================================
  Coverage   93.51%   93.51%           
=======================================
  Files         172      172           
  Lines        6074     6074           
=======================================
  Hits         5680     5680           
  Misses        335      335           
  Partials       59       59           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.