Skip to content

feat: Add Tuple as a GitHub sponsor#811

Merged
yamadashy merged 5 commits intomainfrom
chore/sponsor-tuple
Aug 30, 2025
Merged

feat: Add Tuple as a GitHub sponsor#811
yamadashy merged 5 commits intomainfrom
chore/sponsor-tuple

Conversation

@yamadashy
Copy link
Owner

Summary

  • Add Tuple as a new GitHub sponsor to README.md and website
  • Add Tuple sponsorship image and proper branding
  • Include Tuple in both README and website sponsors page (English)

Changes

  • README.md: Add Tuple sponsor section below Warp with image and description
  • Website: Add Tuple sponsor section to English sponsors.md page
  • Assets: Add Tuple sponsorship image to website assets

Test plan

  • Verify image displays correctly in README.md
  • Verify image displays correctly on website sponsors page
  • Verify all links work correctly and point to https://tuple.app/repomix
  • Verify formatting matches existing sponsor entries

- Add Tuple sponsorship section to README.md below Warp
- Include Tuple logo image and description text
- Link to https://tuple.app/repomix
Copilot AI review requested due to automatic review settings August 30, 2025 04:45
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Aug 30, 2025

Note

Other AI code review bot(s) detected

CodeRabbit has detected other AI code review bot(s) in this pull request and will avoid duplicating their findings in the review comments. This may lead to a less comprehensive review.

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

Adds a Tuple sponsor block to README and sponsors guide alongside existing Warp sponsor. Introduces a new strict JSON Schema (Draft-07) for repomix.config.json at website/client/src/public/schemas/1.4.1/schema.json. No code logic changed.

Changes

Cohort / File(s) Summary of changes
Sponsorship content (docs)
README.md, website/client/src/en/guide/sponsors.md
Inserted a new Tuple sponsor section after the existing Warp sponsor, including link, image, and brief description; no other content altered.
Configuration schema (new)
website/client/src/public/schemas/1.4.1/schema.json
Added Draft-07 JSON Schema for repomix.config.json with strict properties for input, output (incl. git settings), include/ignore, security, and tokenCount; disallows additionalProperties throughout.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch chore/sponsor-tuple

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
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

‼️ IMPORTANT
Auto-reply has been disabled for this repository in the CodeRabbit settings. The CodeRabbit bot will not respond to your replies unless it is explicitly tagged.

  • 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.
  • 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

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

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

  • Add @coderabbitai ignore or @coderabbit 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.

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • 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.

@claude
Copy link
Contributor

claude bot commented Aug 30, 2025

Claude encountered an error —— View job


I'll analyze this and get back to you.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Summary of Changes

Hello @yamadashy, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request aims to formally recognize Tuple as a new sponsor by incorporating their branding and information into the project's main README.md file and the dedicated sponsors page on the website. The changes ensure that Tuple's support is prominently displayed and accessible to users.

Highlights

  • New Sponsor Integration: Integrated Tuple as a new GitHub sponsor across the project's public-facing materials.
  • Content Updates: Updated README.md and the website's English sponsors page (website/client/src/en/guide/sponsors.md) to feature Tuple.
  • Branding and Links: Included Tuple's sponsorship image and ensured correct branding and links pointing to https://tuple.app/repomix.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR adds Tuple as a new GitHub sponsor to the project's README and website by including their sponsorship image, description, and branding across both platforms.

  • Adds Tuple sponsor section to README.md with proper formatting and image
  • Includes Tuple in the website's English sponsors page with consistent styling
  • References sponsorship image assets for both platforms

Reviewed Changes

Copilot reviewed 3 out of 4 changed files in this pull request and generated 2 comments.

File Description
README.md Adds new Tuple sponsor section after header with image and description
website/client/src/en/guide/sponsors.md Adds Tuple sponsor section to website sponsors page with matching format

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request adds Tuple as a new GitHub sponsor. My review focuses on ensuring consistency with existing sponsor entries and the correct display of assets. I've identified a broken image link in the README.md and formatting inconsistencies in both the README and the website's sponsors page. Code suggestions are provided to fix these issues.

@cloudflare-workers-and-pages
Copy link

cloudflare-workers-and-pages bot commented Aug 30, 2025

Deploying repomix with  Cloudflare Pages  Cloudflare Pages

Latest commit: c4decd4
Status: ✅  Deploy successful!
Preview URL: https://92cfc94a.repomix.pages.dev
Branch Preview URL: https://chore-sponsor-tuple.repomix.pages.dev

View logs

@yamadashy yamadashy force-pushed the chore/sponsor-tuple branch from 6c72b7f to 3db88e1 Compare August 30, 2025 04:48
yamadashy and others added 2 commits August 30, 2025 13:50
- Add Tuple sponsorship section to English sponsors.md
- Include Tuple logo and description with proper link
- Link to https://tuple.app/repomix
@yamadashy yamadashy force-pushed the chore/sponsor-tuple branch from a27745b to e638d50 Compare August 30, 2025 04:51
@codecov
Copy link

codecov bot commented Aug 30, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 87.41%. Comparing base (255b99f) to head (c4decd4).
⚠️ Report is 6 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #811   +/-   ##
=======================================
  Coverage   87.41%   87.41%           
=======================================
  Files         113      113           
  Lines        6493     6493           
  Branches     1331     1331           
=======================================
  Hits         5676     5676           
  Misses        817      817           

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

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

- Create shared/sponsors-section.md for centralized sponsor management
- Update all 12 language versions to use VitePress include functionality
- Replace duplicate sponsor HTML with <!--@include: ../../shared/sponsors-section.md-->
- Maintain language-specific content while sharing sponsor information
- Improve maintainability by having single source of truth for sponsors

This change ensures all sponsor updates only need to be made in one place,
reducing maintenance overhead and preventing inconsistencies across languages.
- Add sponsors list image to shared sponsors-section.md for complete centralization
- Update all language versions of index.md to use shared sponsors-section include
- Update all language versions of guide/index.md to use shared sponsors-section include
- Remove duplicate sponsors content from all homepage and guide pages
- Ensure consistent sponsor display across all 36+ website pages in 12 languages

This completes the sponsor content centralization, ensuring all sponsor updates
only need to be made in website/client/src/shared/sponsors-section.md while
maintaining consistency across homepage, guide, and sponsors pages.
@yamadashy yamadashy merged commit 50c31e8 into main Aug 30, 2025
169 of 198 checks passed
@yamadashy yamadashy deleted the chore/sponsor-tuple branch August 30, 2025 05:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants