Add sponsor to readme

[jjw24]

Add sponsor 🥇

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

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.

[coderabbitai]

📝 Walkthrough

Walkthrough

The changes in this pull request focus on enhancing the README.md file for the Flow Launcher project. New sections have been added, including "New changes," "Contributing," and "Developing/Debugging." These additions aim to provide clearer guidance on tracking changes, encouraging contributions, and setting up the development environment, respectively. The updates improve the overall documentation, making it more informative for users and contributors.

Changes

File	Change Summary
README.md	Added "New changes," "Contributing," and "Developing/Debugging" sections to enhance documentation.

Possibly related PRs

• Add Sponsor in Readme.Md #2810: This PR modifies the README.md file by adding a new sponsor, which is related to the documentation updates in the main PR.
• Add sponsor #2885: This PR also adds a contributor link in the README.md, enhancing the documentation, similar to the changes made in the main PR.

Suggested labels

enhancement

🐰 In the garden of code, we hop with glee,
New sections in README, as bright as can be!
With guidance for all, both near and far,
Join us in coding, you'll be a star!
So read and contribute, let’s grow this space,
Together we flourish, in this joyful place! 🌼

---

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.

[coderabbitai]

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (1)

README.md (1)

353-353: Add alt text for sponsor avatars.

Please add descriptive alt text to the sponsor avatars for better accessibility.

Apply this change:

-  <a href="https://github.com/Mavrik327"><img src="https://avatars.githubusercontent.com/u/121626149?v=4" width="10%" /></a>
+  <a href="https://github.com/Mavrik327"><img src="https://avatars.githubusercontent.com/u/121626149?v=4" width="10%" alt="Mavrik327's avatar" /></a>
-  <a href="https://github.com/tikkatek"><img src="https://avatars.githubusercontent.com/u/26571381?v=4" width="10%" /></a>
+  <a href="https://github.com/tikkatek"><img src="https://avatars.githubusercontent.com/u/26571381?v=4" width="10%" alt="tikkatek's avatar" /></a>
-  <a href="https://github.com/patrickdobler"><img src="https://avatars.githubusercontent.com/u/16536946?v=4" width="10%" /></a>
+  <a href="https://github.com/patrickdobler"><img src="https://avatars.githubusercontent.com/u/16536946?v=4" width="10%" alt="patrickdobler's avatar" /></a>
-  <a href="https://github.com/benflap"><img src="https://avatars.githubusercontent.com/u/62034481?v=4" width="10%" /></a>
+  <a href="https://github.com/benflap"><img src="https://avatars.githubusercontent.com/u/62034481?v=4" width="10%" alt="benflap's avatar" /></a>

🧰 Tools

🪛 Markdownlint

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

(MD045, no-alt-text)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 50c00f3 and 9786fd7.

📒 Files selected for processing (1)

• README.md (1 hunks)

🧰 Additional context used

🪛 Markdownlint

README.md

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

(MD045, no-alt-text)

🔇 Additional comments (1)

README.md (1)

Line range hint 341-359: LGTM! Well-structured sponsor section.

The sponsor section is well-organized with:

• Clear hierarchy for different sponsor tiers
• Consistent styling and layout
• Proper attribution and links to sponsors

🧰 Tools

🪛 Markdownlint

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

(MD045, no-alt-text)

---

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

(MD045, no-alt-text)

---

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

(MD045, no-alt-text)

---

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

(MD045, no-alt-text)

---

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

(MD045, no-alt-text)

---

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

(MD045, no-alt-text)

---

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

(MD045, no-alt-text)