Skip to content

chore(sponsors): Remove Tuple from sponsor list#1192

Merged
yamadashy merged 1 commit intomainfrom
chore/remove-tuple-sponsor
Mar 3, 2026
Merged

chore(sponsors): Remove Tuple from sponsor list#1192
yamadashy merged 1 commit intomainfrom
chore/remove-tuple-sponsor

Conversation

@yamadashy
Copy link
Owner

@yamadashy yamadashy commented Mar 3, 2026

Tuple has ended their sponsorship, so remove their entry from the sponsor lists.

Checklist

  • Run npm run test
  • Run npm run lint

Open with Devin

Tuple has ended their sponsorship, so remove their entry from
README.md and website sponsors section.
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Mar 3, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8549015 and da45659.

📒 Files selected for processing (2)
  • README.md
  • website/client/src/shared/sponsors-section.md
💤 Files with no reviewable changes (2)
  • README.md
  • website/client/src/shared/sponsors-section.md

📝 Walkthrough

Walkthrough

This pull request removes the Tuple sponsorship block from two documentation files: README.md and the website sponsors section. The remaining sponsor entries (Warp and Tower) are preserved, with spacing adjusted accordingly.

Changes

Cohort / File(s) Summary
Sponsorship Block Removal
README.md, website/client/src/shared/sponsors-section.md
Removed Tuple sponsorship references including anchor, image, and description; other sponsors remain intact.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly summarizes the main change: removing Tuple from the sponsor list, which matches the changeset content.
Description check ✅ Passed The description includes the required context explaining why Tuple was removed and follows the repository template with the checklist section.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

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

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

Comment @coderabbitai help to get the list of available commands and usage tips.

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello, 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 addresses the conclusion of Tuple's sponsorship by meticulously removing all associated entries from the project's documentation. The changes ensure that the sponsor lists accurately reflect current partnerships, maintaining up-to-date information for users and contributors.

Highlights

  • Sponsor Removal: Removed Tuple from the project's sponsor lists in both the main README and the dedicated sponsors section.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog
  • README.md
    • Removed the HTML block and Markdown heading related to Tuple's sponsorship.
  • website/client/src/shared/sponsors-section.md
    • Removed the HTML block and Markdown link associated with Tuple's sponsorship.
Activity
  • The pull request was opened by yamadashy with the clear intent to remove Tuple from the sponsor list.
  • The description includes a checklist for running npm run test and npm run lint, indicating standard pre-merge verification steps.
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 by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

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 pull request 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

@devin-ai-integration devin-ai-integration bot left a comment

Choose a reason for hiding this comment

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

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 1 additional finding.

Open in Devin Review

@claude
Copy link
Contributor

claude bot commented Mar 3, 2026

PR Review: chore(sponsors): Remove Tuple from sponsor list

Summary

Clean, straightforward PR that removes Tuple's sponsorship entries from README.md and website/client/src/shared/sponsors-section.md. The diff is deletions-only with no logic changes, so there's minimal risk.

Findings

Leftover asset file

The Tuple sponsor image is still present in the repository:

website/client/src/public/images/sponsors/tuple/github_repo_sponsorship.png

Consider removing this file (and the tuple/ directory) in this PR or a follow-up to avoid shipping unused assets.

Detailed review notes

Code quality: The removals are clean. No surrounding markup was broken — spacing and structure of the remaining sponsors (Warp, Tower) look correct in both files.

Potential bugs: None. The HTML structure remains valid after the deletions.

Security concerns: None.

Performance: Removing the leftover image would save a small amount of repo size, but this is non-critical.

Test coverage: No tests needed for content-only sponsor section changes.

Premortem analysis:

  • Rendering issue: Verified that the remaining sponsor sections in both README.md and sponsors-section.md have correct spacing and structure — no extra blank lines or broken HTML. Looks good.
  • Stale references: No other references to "tuple" remain in the codebase text, but the image file at website/client/src/public/images/sponsors/tuple/github_repo_sponsorship.png is now orphaned.

Verdict: Looks good to merge. The only suggestion is to also remove the orphaned image file website/client/src/public/images/sponsors/tuple/github_repo_sponsorship.png.

@codecov
Copy link

codecov bot commented Mar 3, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 87.14%. Comparing base (8549015) to head (da45659).
⚠️ Report is 4 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1192   +/-   ##
=======================================
  Coverage   87.14%   87.14%           
=======================================
  Files         115      115           
  Lines        4310     4310           
  Branches      998      998           
=======================================
  Hits         3756     3756           
  Misses        554      554           

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

@cloudflare-workers-and-pages
Copy link

Deploying repomix with  Cloudflare Pages  Cloudflare Pages

Latest commit: da45659
Status: ✅  Deploy successful!
Preview URL: https://49f5259d.repomix.pages.dev
Branch Preview URL: https://chore-remove-tuple-sponsor.repomix.pages.dev

View logs

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 removes Tuple's sponsorship information from two Markdown files. The changes are straightforward, but they leave behind some extra blank lines in the source. I've added suggestions to remove them for improved readability. As a follow-up, you might also consider removing the now-unused sponsor image files from the repository to keep it clean.

Note: Security Review has been skipped due to the limited scope of the PR.

@yamadashy yamadashy merged commit bf4e45e into main Mar 3, 2026
58 checks passed
@yamadashy yamadashy deleted the chore/remove-tuple-sponsor branch March 3, 2026 14:58
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.

1 participant