Skip to content

keyv - docs: Move Bun Support section lower in README#1853

Merged
jaredwray merged 1 commit intomainfrom
claude/move-bun-support-section-5ZTss
Feb 22, 2026
Merged

keyv - docs: Move Bun Support section lower in README#1853
jaredwray merged 1 commit intomainfrom
claude/move-bun-support-section-5ZTss

Conversation

@jaredwray
Copy link
Owner

Move the Bun Support section from near the top (after Features) to
near the bottom (before How to Contribute) to better reflect its
secondary importance relative to core documentation.

https://claude.ai/code/session_012LBXt6cRT3hkaVVCwAGz1J

Move the Bun Support section from near the top (after Features) to
near the bottom (before How to Contribute) to better reflect its
secondary importance relative to core documentation.

https://claude.ai/code/session_012LBXt6cRT3hkaVVCwAGz1J
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @jaredwray, 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 refactors the README.md file by repositioning the 'Bun Support' section. The intent is to improve the logical flow and hierarchy of information within the documentation, ensuring that core features and usage instructions are presented before runtime-specific details.

Highlights

  • Documentation Reorganization: The 'Bun Support' section in core/keyv/README.md has been relocated from a prominent position near the top (after 'Features') to a less prominent position near the bottom (before 'How to Contribute'). This change aims to reflect its secondary importance compared to core documentation topics.
Changelog
  • core/keyv/README.md
    • Moved the 'Bun Support' section and its corresponding entry in the Table of Contents from the top to the bottom of the document.
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

@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

The pull request successfully moves the "Bun Support" section to a more appropriate location near the end of the README, as intended. This change improves the documentation's flow by prioritizing core usage and API details while maintaining visibility for runtime compatibility information. The Table of Contents has been updated correctly, and the formatting remains consistent with the rest of the document.

@codecov
Copy link

codecov bot commented Feb 22, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.95%. Comparing base (4725c4e) to head (1830b04).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1853   +/-   ##
=======================================
  Coverage   99.95%   99.95%           
=======================================
  Files          32       32           
  Lines        2434     2434           
  Branches      440      440           
=======================================
  Hits         2433     2433           
  Misses          1        1           

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

@jaredwray jaredwray merged commit 5bd9166 into main Feb 22, 2026
10 checks passed
@jaredwray jaredwray deleted the claude/move-bun-support-section-5ZTss branch February 22, 2026 00:35
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