Add new sponsor to README

[Yusyuriv]

Wasn't sure where to put the new sponsor, if I placed them incorrectly, feel free to correct me.

[gitstream-cm]

🥷 Code experts: jjw24, VictoriousRaptor

jjw24 has most 👩‍💻 activity in the files.
VictoriousRaptor, jjw24 have most 🧠 knowledge in the files.

See details

README.md

Activity based on git-commit:

	jjw24
MAR
FEB
JAN
DEC
NOV	1 additions & 0 deletions
OCT

Knowledge based on git-blame:
VictoriousRaptor: 31%
jjw24: 26%

To learn more about /:\ gitStream - Visit our Docs

[github-actions]

@check-spelling-bot Report

🔴 Please review

See the 📂 files view, the 📜action log, or 📝 job summary for details.

❌ Errors	Count
ℹ️ candidate-pattern	1
❌ forbidden-pattern	22
⚠️ ignored-expect-variant	1
⚠️ non-alpha-in-dictionary	19

See ❌ Event descriptions for more information.

Using only_check_changed_files is incompatible with expect.txt.
To accept the items listed, you should add them to allow.txt.

Pattern suggestions ✂️ (1)

You could add these patterns to .github/actions/spelling/patterns.txt:

# Automatically suggested patterns

# hit-count: 1 file-count: 1
# Non-English
[a-zA-Z]*[ÀÁÂÃÄÅÆÇÈÉÊËÌÍÎÏÐÑÒÓÔÕÖØÙÚÛÜÝßàáâãäåæçèéêëìíîïðñòóôõöøùúûüýÿĀāŁłŃńŅņŒœŚśŠšŜŝŸŽžź][a-zA-Z]{3}[a-zA-ZÀÁÂÃÄÅÆÇÈÉÊËÌÍÎÏÐÑÒÓÔÕÖØÙÚÛÜÝßàáâãäåæçèéêëìíîïðñòóôõöøùúûüýÿĀāŁłŃńŅņŒœŚśŠšŜŝŸŽžź]*

If the flagged items are 🤯 false positives

If items relate to a ...

• binary file (or some other file you wouldn't want to check at all).

  Please add a file path to the excludes.txt file matching the containing file.

  File paths are Perl 5 Regular Expressions - you can test yours before committing to verify it will match your files.

  ^ refers to the file's path from the root of the repository, so ^README\.md$ would exclude README.md (on whichever branch you're using).

• well-formed pattern.

  If you can write a pattern that would match it,
  try adding it to the patterns.txt file.

  Patterns are Perl 5 Regular Expressions - you can test yours before committing to verify it will match your lines.

  Note that patterns can't match multiline strings.

[gitstream-cm]

Be a legend 🏆 by adding a before and after screenshot of the changes you made, especially if they are around UI/UX.

[coderabbitai]

📝 Walkthrough

Walkthrough

The README.md file has been updated to include an additional sponsor link and logo. The changes insert a new anchor tag linking to a GitHub profile with an associated image tag for the user's avatar. Line breaks were adjusted to maintain consistent formatting in the sponsorship section. No modifications were made to exported entities.

Changes

File(s)	Change Summary
README.md	Added a new sponsor link (https://github.com/AjmalParkar006) and corresponding image; adjusted line breaks in the sponsorship section layout.

Possibly related PRs

• Add Sponsor in Readme.Md #2810: Added a sponsor link and logo in the README.md, directly related to this update.
• Add sponsor to readme #3064: Focused on enhancing the sponsorship section in the README.md with similar modifications.

Suggested reviewers

• Garulf
• jjw24
• VictoriousRaptor
• onesounds
• deefrawley
• taooceros
• z1nc0r3

Poem

In the digital field, I hop with delight,
A new sponsor blooms in the README light.
Line breaks align like paths so true,
A sponsor’s badge joins our crew.
I’m just a rabbit, thrilled with the view!
🥕🐇

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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 generate docstrings to generate docstrings for this 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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

README.md (1)

342-344: Accessibility Improvement: Add Alt Attribute to New Sponsor Image

The new sponsor link for AjmalParkar006 is correctly added. However, the <img> tag lacks an alt attribute, which is important for accessibility and to satisfy markdown lint rules (MD045). Consider adding descriptive alt text (e.g., "Ajmal Parkar Sponsor Logo").

Diff suggestion:

-  <a href="/AjmalParkar006">
-    <img src='https://avatars.githubusercontent.com/u/76547256?v=4' width="10%"/>
-  </a>
+  <a href="/AjmalParkar006">
+    <img src='https://avatars.githubusercontent.com/u/76547256?v=4' width="10%" alt="Ajmal Parkar Sponsor Logo"/>
+  </a>

🧰 Tools

🪛 markdownlint-cli2 (0.17.2)

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

(MD045, no-alt-text)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5881da8 and f2c3034.

📒 Files selected for processing (1)

• README.md (1 hunks)

🧰 Additional context used

🪛 markdownlint-cli2 (0.17.2)

README.md

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

(MD045, no-alt-text)

---

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

(MD045, no-alt-text)

⏰ Context from checks skipped due to timeout of 90000ms (4)

• GitHub Check: gitStream workflow automation
• GitHub Check: gitStream.cm
• GitHub Check: gitStream.cm
• GitHub Check: gitStream.cm

🔇 Additional comments (1)

README.md (1)

337-338: Formatting Enhancement: Additional Line Breaks

The insertion of two <br /> tags helps visually separate the sponsor logos and maintains an organized layout. Please verify that this extra spacing renders well across various devices and screen sizes.