Skip to content

Conversation

@scidomino
Copy link
Collaborator

Summary

When buffering fast returns, emit them as shift+return instead of shiftless.

Details

We were previously accidentally relying on name: '', to make this not be treated as a return. When I fixed that to name: 'return', that caused this to stop being treated as a newline.

How to Validate

Copy paste text with a newline in an editor that doesn't support bracketed paste.

Pre-Merge Checklist

  • Updated relevant documentation and README (if needed)
  • Added/updated tests (if needed)
  • Noted breaking changes (if any)
  • Validated on required platforms/methods:
    • MacOS
      • npm run
      • npx
      • Docker
      • Podman
      • Seatbelt
    • Windows
      • npm run
      • npx
      • Docker
    • Linux
      • npm run
      • npx
      • Docker

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @scidomino, 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 resolves a regression where fast returns, particularly when buffering, were no longer correctly interpreted as newlines. By explicitly setting modifier keys (shift, alt, ctrl, cmd) when emitting the 'return' key event, the system now correctly distinguishes between a submission and a newline, restoring expected behavior for text input.

Highlights

  • Correct Newline Emission: Modified packages/cli/src/ui/contexts/KeypressContext.tsx to ensure buffered fast returns are emitted as shift+return to correctly represent a newline, rather than a submission. This addresses a regression introduced by a previous change that made name: 'return' explicit.
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

This pull request aims to fix an issue where buffered fast returns, such as those from pasting text, are incorrectly treated as submissions instead of newlines. The change correctly modifies the keypress event to represent a shift+return by setting shift: true and explicitly resetting other modifiers to false. This ensures that pasted newlines are handled as newlines within the input, which is the desired behavior. The implementation is straightforward and effectively addresses the described bug. The change looks correct.

@github-actions
Copy link

github-actions bot commented Jan 22, 2026

Size Change: +130 B (0%)

Total Size: 23.2 MB

ℹ️ View Unchanged
Filename Size Change
./bundle/gemini.js 23.2 MB +130 B (0%)
./bundle/sandbox-macos-permissive-closed.sb 1.03 kB 0 B
./bundle/sandbox-macos-permissive-open.sb 890 B 0 B
./bundle/sandbox-macos-permissive-proxied.sb 1.31 kB 0 B
./bundle/sandbox-macos-restrictive-closed.sb 3.29 kB 0 B
./bundle/sandbox-macos-restrictive-open.sb 3.36 kB 0 B
./bundle/sandbox-macos-restrictive-proxied.sb 3.56 kB 0 B

compressed-size-action

@scidomino scidomino marked this pull request as ready for review January 22, 2026 19:27
@scidomino scidomino requested a review from a team as a code owner January 22, 2026 19:27
@gemini-cli gemini-cli bot added the status/need-issue Pull requests that need to have an associated issue. label Jan 22, 2026
@scidomino scidomino enabled auto-merge January 22, 2026 19:31
Copy link
Collaborator

@jacob314 jacob314 left a comment

Choose a reason for hiding this comment

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

lgtm

@scidomino scidomino added this pull request to the merge queue Jan 22, 2026
Merged via the queue into main with commit addb57c Jan 22, 2026
25 checks passed
@scidomino scidomino deleted the tomm_fix branch January 22, 2026 20:03
@scidomino
Copy link
Collaborator Author

/patch preview

@github-actions
Copy link

Patch workflow(s) dispatched successfully!

📋 Details:

  • Channels: preview
  • Commit: addb57c31f4ce92d959522a81208bed164e8ddfc
  • Workflows Created: 1

🔗 Track Progress:

github-actions bot pushed a commit that referenced this pull request Jan 22, 2026
# Conflicts:
#	packages/cli/src/ui/contexts/KeypressContext.test.tsx
@github-actions
Copy link

🚀 Patch PR Created!

📋 Patch Details:

📝 Next Steps:

  1. ⚠️ Resolve conflicts in the hotfix PR first: #17345
  2. Test your changes after resolving conflicts
  3. Once merged, the patch release will automatically trigger
  4. You'll receive updates here when the release completes

🔗 Track Progress:

scidomino added a commit that referenced this pull request Jan 22, 2026
@github-actions
Copy link

🚀 Patch Release Started!

📋 Release Details:

  • Environment: prod
  • Channel: preview → publishing to npm tag preview
  • Version: v0.26.0-preview.2
  • Hotfix PR: Merged ✅
  • Release Branch: release/v0.26.0-preview.2-pr-17331

⏳ Status: The patch release is now running. You'll receive another update when it completes.

🔗 Track Progress:

@github-actions
Copy link

Patch Release Complete!

📦 Release Details:

🎉 Status: Your patch has been successfully released and published to npm!

📝 What's Available:

🔗 Links:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

status/need-issue Pull requests that need to have an associated issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants