Skip to content

feat(docs): Add sponsors badge and improve documentation transparency#639

Merged
yamadashy merged 6 commits intomainfrom
chore/docs
Jun 7, 2025
Merged

feat(docs): Add sponsors badge and improve documentation transparency#639
yamadashy merged 6 commits intomainfrom
chore/docs

Conversation

@yamadashy
Copy link
Copy Markdown
Owner

Summary

  • Add sponsors badge to all website language index pages (12 languages) for consistent sponsor visibility
  • Add sponsors badge to README.md after project description for prominent recognition
  • Fix missing JSNation Open Source Awards link in Japanese website version
  • Update privacy policy to clarify temporary file processing and automatic deletion on website

Test plan

  • Verify sponsors badge displays correctly on all language versions of website
  • Verify sponsors badge displays correctly in README.md
  • Verify JSNation Open Source Awards link works in Japanese version
  • Verify privacy policy language is clear and accurate
  • Confirm all documentation changes maintain consistency across languages

🤖 Generated with Claude Code

yamadashy and others added 4 commits June 7, 2025 11:11
Add GitHub sponsors badge to homepage across all 12 language versions
for consistent sponsor visibility and recognition.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
…e version

Add missing link to JSNation Open Source Awards 2025 in Japanese index page
to match all other language versions.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
Add GitHub sponsors badge prominently after project description
for better sponsor visibility and recognition.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
Add explanation about temporary server storage of uploaded files
and automatic deletion after processing for transparency.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings June 7, 2025 03:14
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Jun 7, 2025

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

Sponsor badges linking to the GitHub Sponsors page for "yamadashy" were added to the main README and all localized website index files. The README's privacy policy section was expanded to clarify the handling of uploaded ZIP files. The Japanese index also updated the awards nomination section with a hyperlink.

Changes

Files Change Summary
README.md Added sponsor badge; expanded privacy policy regarding uploaded ZIP file handling.
website/client/src/{de,en,es,fr,hi,id,ja,ko,pt-br,vi,zh-cn,zh-tw}/... Inserted sponsor badge linking to GitHub Sponsors in each localized index file; ja/index.md also updated awards section.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Website (Localized Index)
    participant GitHub Sponsors

    User->>Website (Localized Index): Loads homepage
    Website (Localized Index)->>User: Renders sponsor badge with link
    User->>GitHub Sponsors: Clicks sponsor badge
    GitHub Sponsors-->>User: Displays sponsorship page
Loading

Possibly related PRs

  • improve README.md #265: Both PRs focus on improving the README.md file content, specifically enhancing documentation and user information, without altering code or exported entities.

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

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.

Copy link
Copy Markdown
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.

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!

Summary of Changes

Hello! Gemini or gemini-code-assist here, providing a summary of this pull request by @yamadashy. This PR focuses on enhancing the project's documentation and transparency. The main changes involve adding sponsor badges to prominent locations, fixing a specific link in the Japanese documentation, and providing more clarity in the privacy policy regarding file handling on the website.

Highlights

  • Sponsor Visibility: Adds a sponsor badge to the main README.md file and the index pages for all 12 language versions of the project website to increase visibility for sponsors.
  • Documentation Accuracy: Corrects a missing link to the JSNation Open Source Awards in the Japanese version of the website's index page.
  • Privacy Policy Clarity: Updates the privacy policy section in README.md to explicitly state that uploaded files for processing are temporarily stored and automatically deleted immediately after processing.

Changelog

Click here to see the changelog
  • README.md
    • Added sponsors badge image and link after the project description.
    • Added a line to the privacy policy clarifying temporary file storage and automatic deletion for file processing.
  • website/client/src/de/index.md
    • Added sponsors badge image and link.
  • website/client/src/en/index.md
    • Added sponsors badge image and link.
  • website/client/src/es/index.md
    • Added sponsors badge image and link.
  • website/client/src/fr/index.md
    • Added sponsors badge image and link.
  • website/client/src/hi/index.md
    • Added sponsors badge image and link.
  • website/client/src/id/index.md
    • Added sponsors badge image and link.
  • website/client/src/ja/index.md
    • Added sponsors badge image and link.
    • Added the missing link to the JSNation Open Source Awards.
  • website/client/src/ko/index.md
    • Added sponsors badge image and link.
  • website/client/src/pt-br/index.md
    • Added sponsors badge image and link.
  • website/client/src/vi/index.md
    • Added sponsors badge image and link.
  • website/client/src/zh-cn/index.md
    • Added sponsors badge image and link.
  • website/client/src/zh-tw/index.md
    • Added sponsors badge image and link.
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 is currently in preview and 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 to provide feedback.

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.

@cloudflare-workers-and-pages
Copy link
Copy Markdown

cloudflare-workers-and-pages bot commented Jun 7, 2025

Deploying repomix with  Cloudflare Pages  Cloudflare Pages

Latest commit: dcaaacf
Status: ✅  Deploy successful!
Preview URL: https://6c06924a.repomix.pages.dev
Branch Preview URL: https://chore-docs.repomix.pages.dev

View logs

Copy link
Copy Markdown
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 improves documentation transparency by adding a sponsors badge to multiple language index pages and the README while clarifying the file processing policy.

  • Inserts a sponsors badge link consistently across 12 website language pages.
  • Fixes an issue with the JSNation Open Source Awards link in the Japanese version.
  • Updates the privacy policy text in the README to specify details on temporary file processing.

Reviewed Changes

Copilot reviewed 13 out of 13 changed files in this pull request and generated 1 comment.

Show a summary per file
File Description
website/client/src/zh-tw/index.md Added sponsors badge before the awards nomination section
website/client/src/zh-cn/index.md Added sponsors badge before the awards nomination section
website/client/src/vi/index.md Added sponsors badge before the awards nomination section
website/client/src/pt-br/index.md Added sponsors badge before the awards nomination section
website/client/src/ko/index.md Added sponsors badge before the awards nomination section
website/client/src/ja/index.md Added sponsors badge and updated the awards link formatting
website/client/src/id/index.md Added sponsors badge before the awards nomination section
website/client/src/hi/index.md Added sponsors badge before the awards nomination section
website/client/src/fr/index.md Added sponsors badge before the awards nomination section
website/client/src/es/index.md Added sponsors badge before the awards nomination section
website/client/src/en/index.md Added sponsors badge before the awards nomination section
website/client/src/de/index.md Added sponsors badge before the awards nomination section
README.md Added sponsors badge and clarified file processing details
Comments suppressed due to low confidence (1)

README.md:1257

  • Ensure that the updated file processing information is fully aligned with internal privacy policies, and consider adding details on retention duration if applicable.
- **File Processing**: When uploading ZIP files or folders, your files are temporarily stored on our servers for processing. All uploaded files and processed data are automatically deleted immediately after processing is complete.

@codecov
Copy link
Copy Markdown

codecov bot commented Jun 7, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.32%. Comparing base (583d538) to head (dcaaacf).
Report is 7 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #639   +/-   ##
=======================================
  Coverage   90.32%   90.32%           
=======================================
  Files          96       96           
  Lines        4962     4962           
  Branches     1042     1042           
=======================================
  Hits         4482     4482           
  Misses        480      480           

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

Copy link
Copy Markdown
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 effectively adds sponsor visibility and improves documentation transparency. The changes are consistent and the link fix is appreciated. I have two main suggestions related to accessibility of the new sponsor badges on localized website pages and clarification on the privacy policy's reach.

Summary of Findings

  • Accessibility of Sponsor Badge Alt Text: The alt text for the newly added sponsor badges on the 11 non-English website index pages is currently in English ("Sponsors"). For better accessibility, this text should be translated into the respective language of each page. This was raised as a review comment.
  • Privacy Policy Update Scope: The privacy policy clarification regarding temporary file processing has been added to the README.md. It's important to confirm if a separate privacy policy page on the repomix.com website also requires this update for consistency. This was raised as a review comment.
  • README Sponsor Badge Accessibility: The sponsor badge added to the README is missing alt text, which impacts accessibility. Adding alt="Sponsors" would improve this.

Merge Readiness

The pull request introduces valuable improvements. However, before merging, I recommend addressing the medium severity issues raised: ensuring the accessibility of the sponsor badge alt text on localized pages and clarifying the scope of the privacy policy update with respect to any dedicated privacy page on repomix.com. Also, adding alt text to the README sponsor badge would be beneficial. Once these points are clarified or addressed, the PR should be in good shape. As an AI, I am not authorized to approve pull requests; please ensure further review and approval by team members.


<div class="cli-section">

[![Sponsors](https://cdn.jsdelivr.net/gh/yamadashy/sponsor-list/sponsors/sponsors.svg)](https://github.com/sponsors/yamadashy)
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

The alt text for the new sponsors badge is currently "Sponsors" (English). For improved accessibility on localized pages like this German version, web accessibility guidelines recommend translating alt text. 1

Given that this PR modifies all language versions for the badge addition, is there a plan to translate this alt text for each respective language (e.g., "Sponsoren" for German)? Or is the expectation that the maintainer translation process (mentioned in CONTRIBUTING.md) will cover this attribute later?

Using the English alt text on non-English pages is not ideal for accessibility. This consideration applies to the sponsor badges added in all 11 non-English index.md files (de, es, fr, hi, id, ja, ko, pt-br, vi, zh-cn, zh-tw). The English version (en/index.md) can, of course, retain alt="Sponsors".

Style Guide References

Footnotes

  1. W3C WAI (Web Accessibility Initiative) guidelines state: "If an image is part of a page that is translated into several languages, the alternative text should also be translated into these languages." (Source: https://www.w3.org/WAI/tutorials/images/localization/)

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (9)
website/client/src/zh-cn/index.md (1)

29-29: Sponsor badge insertion: The sponsors badge is correctly added within the cli-section as per PR objectives. Consider localizing the alt text "Sponsors" to Chinese (e.g., “赞助者”) for improved accessibility.

website/client/src/de/index.md (1)

29-29: Sponsor badge addition: The sponsorship badge is correctly positioned above the awards section. Optionally, translate the alt text "Sponsors" to German (e.g., “Sponsoren”) for better localization.

website/client/src/id/index.md (1)

29-29: Sponsor badge insertion: Correctly added before the awards section. Consider translating the alt text "Sponsors" to Indonesian (e.g., “Sponsor”) to match the document language.

website/client/src/pt-br/index.md (1)

29-29: Sponsor badge added: Badge is correctly placed inside cli-section. Consider translating the alt text "Sponsors" into Portuguese (e.g., “Patrocinadores”) for localization.

website/client/src/hi/index.md (1)

29-29: Sponsor badge addition: The badge is appropriately inserted before the awards section. Consider localizing the alt text "Sponsors" to Hindi (e.g., “प्रायोजक”) to enhance accessibility.

website/client/src/fr/index.md (1)

26-26: Check sponsor badge accessibility.
The inserted badge aligns with other locales, but consider making the alt text more descriptive (for example, alt="Sponsors of Repomix") to improve screen‐reader support.

website/client/src/ja/index.md (1)

29-29: Ensure badge accessibility and consistency.
The sponsor badge placement is correct. For better accessibility, update the alt attribute to something like alt="Sponsors of Repomix".

README.md (2)

52-52: Consolidate sponsor badges.
There’s already a GitHub Sponsors badge at line 42. To avoid redundancy, consider replacing that static badge with the dynamic jsdelivr version—or vice versa—and keep one.


1257-1257: Align privacy policy bullet style.
The new file-processing bullet is clear, but ensure its indentation, punctuation, and formatting (e.g., trailing period) match the neighboring bullets for consistency.

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 583d538 and 14da1e5.

📒 Files selected for processing (13)
  • README.md (2 hunks)
  • website/client/src/de/index.md (1 hunks)
  • website/client/src/en/index.md (1 hunks)
  • website/client/src/es/index.md (1 hunks)
  • website/client/src/fr/index.md (1 hunks)
  • website/client/src/hi/index.md (1 hunks)
  • website/client/src/id/index.md (1 hunks)
  • website/client/src/ja/index.md (1 hunks)
  • website/client/src/ko/index.md (1 hunks)
  • website/client/src/pt-br/index.md (1 hunks)
  • website/client/src/vi/index.md (1 hunks)
  • website/client/src/zh-cn/index.md (1 hunks)
  • website/client/src/zh-tw/index.md (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (19)
  • GitHub Check: Build and run (macos-latest, 19.x)
  • GitHub Check: Build and run (macos-latest, 23.x)
  • GitHub Check: Build and run (windows-latest, 21.x)
  • GitHub Check: Build and run (macos-latest, 18.x)
  • GitHub Check: Build and run (macos-latest, 20.x)
  • GitHub Check: Build and run (windows-latest, 24.x)
  • GitHub Check: Build and run (windows-latest, 22.x)
  • GitHub Check: Build and run (windows-latest, 20.x)
  • GitHub Check: Build and run (windows-latest, 19.x)
  • GitHub Check: Build and run (windows-latest, 18.x)
  • GitHub Check: Build and run (ubuntu-latest, 21.x)
  • GitHub Check: Build and run (ubuntu-latest, 18.x)
  • GitHub Check: Test (windows-latest, 19.x)
  • GitHub Check: Test (windows-latest, 23.x)
  • GitHub Check: Test (windows-latest, 21.x)
  • GitHub Check: Test (windows-latest, 20.x)
  • GitHub Check: Test (windows-latest, 18.x)
  • GitHub Check: Test (windows-latest, 18.0.0)
  • GitHub Check: Analyze (javascript-typescript)
🔇 Additional comments (6)
website/client/src/zh-tw/index.md (1)

29-29: Sponsor badge insertion looks good

The badge is correctly placed within the cli-section and matches the format used across other locales.

website/client/src/vi/index.md (1)

29-29: Sponsor badge insertion looks good

The badge is correctly placed within the cli-section and matches the format used across other locales.

website/client/src/ko/index.md (1)

29-29: Sponsor badge insertion looks good

The badge is correctly placed within the cli-section and matches the format used across other locales.

website/client/src/en/index.md (1)

29-29: Sponsor badge insertion looks good

The badge is correctly placed within the cli-section and matches the format used across other locales.

website/client/src/es/index.md (1)

29-29: Sponsor badge insertion looks good

The badge is correctly placed within the cli-section and matches the format used across other locales.

website/client/src/ja/index.md (1)

33-33: Verify updated awards hyperlink.
The nomination text now includes the awards link inline. Please confirm the Japanese phrasing reads naturally and that the link styling matches the rest of the site (e.g., target behavior).

yamadashy and others added 2 commits June 7, 2025 12:18
Update sponsors badge URLs from .svg to .png format across all
documentation files for consistent display and proper functionality.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
Add sponsors badge to guide index pages across all 12 languages
for consistent sponsor visibility throughout documentation.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
@yamadashy yamadashy merged commit d757cb4 into main Jun 7, 2025
65 checks passed
@yamadashy yamadashy deleted the chore/docs branch June 7, 2025 06:05
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