Add a Summer of Making badge

[MMK21Hub]

We had a badge for Arcade, so now we have one for Summer of Making 2025 too :D

Here's a mockup I made by giving the same options to shields.io:

I stole the icon from https://github.com/hackclub/summer-of-making/blob/main/public/favicon.png

---

This change is 

Summary by CodeRabbit

• New Features
  • Introduced a new "Summer of Making 2025" badge with a custom icon and updated styling options.

[coderabbitai]

📝 Walkthrough

Walkthrough

A new icon and a corresponding badge entry for "Summer of Making 2025" were added to the JSON configuration file. The icon is provided as a base64-encoded PNG, and the badge includes specific label, color, message, and logo properties, integrated under the "hackclub" static badges section.

Changes

Cohort / File(s)	Change Summary
Badge and Icon Addition lib/cli/kv-seed.json	Added a base64 PNG icon "hackclub-summer-of-making" and a "summer-of-making" badge under "staticBadges.hackclub" with custom label, colors, message, and logo reference.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A badge for summer, bright and new,
With colors warm and message true.
Hackclub’s icon now takes its place,
In JSON fields, a cozy space.
Rabbits hop and softly cheer:
“Summer of Making’s finally here!”
🐰✨

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests 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)

lib/cli/kv-seed.json (1)

6-6: Consider externalising or optimising the embedded PNG to keep the seed file slim

The new hackclub-summer-of-making icon is an inline PNG. At ~20 KB this single line inflates the size of the already-large seed file and makes diffs noisy.
Options:

- "hackclub-summer-of-making": "data:image/png;base64, …"
+ // 1. Host the PNG under /public/icons and reference by URL
+ "hackclub-summer-of-making": "/icons/hackclub-summer-of-making.png"
+
+ // 2. Convert to an optimised SVG (other icons are SVG) and inline that instead

Either keeps the KV seed readable and git-friendly.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between c8265d6 and e6efe00.

📒 Files selected for processing (1)

• lib/cli/kv-seed.json (2 hunks)

🔇 Additional comments (1)

lib/cli/kv-seed.json (1)

24-35: Badge definition looks good and is consistent with existing entries

• Key name, colours, logo reference and null links follow the same conventions as the existing Arcade badge. No issues spotted.