Skip to content

Conversation

@pavelgj
Copy link
Collaborator

@pavelgj pavelgj commented Dec 17, 2025

Checklist (if applicable):

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @pavelgj, 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 an issue where an unintended newline character was being appended to the JSON output of action run streams. By switching to a more explicit JSON marshaling and writing process, the change ensures that the stream's response contains only the intended JSON data, improving the correctness and predictability of the API for consumers.

Highlights

  • Newline Character Removal: The pull request modifies the action run stream handler to prevent an unwanted newline character from being sent at the end of the JSON response.
  • JSON Encoding Method Change: The method for encoding JSON responses has been updated from json.NewEncoder(w).Encode() to a manual json.Marshal() followed by w.Write(data), providing more control over the output.
  • Error Handling for JSON Marshaling: New error handling has been introduced for the json.Marshal operation, ensuring that marshaling failures are caught and an appropriate ReflectionError is returned.
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 an extra newline character is appended to the end of a streaming action response. The change correctly replaces json.NewEncoder(...).Encode() with json.Marshal() followed by w.Write() to avoid the unwanted newline. While the main change is correct, I've found a potential bug in the new error handling logic and provided a suggestion to fix it.

@pavelgj pavelgj changed the title fix(go/core/reflection): do not send new line at the end of action run stream Dec 18, 2025
@pavelgj pavelgj merged commit 2ae424c into main Dec 18, 2025
11 checks passed
@pavelgj pavelgj deleted the pj/fix-reflection-streaming-final-result branch December 18, 2025 16:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

2 participants