Skip to content

Conversation

@traut
Copy link

@traut traut commented Jan 30, 2026

The fix adjust debug messages in ActionDef.runWithTelemetry function: it removes JSON bytes from the debug messages and accompanying JSON marshaling code. Debug messages with raw bytes produce unreadable noisy logs and introduce the risk of unintended data exposure through the logs.

@github-actions github-actions bot added the go label Jan 30, 2026
@traut traut changed the title fix(go): Replace the raw bytes in the debug message with the count of bytes fix(go): Remove raw bytes from the debug messages Jan 30, 2026
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @traut, 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 focuses on improving the quality and security of debug logs by removing the inclusion of raw JSON bytes in the ActionDef.runWithTelemetry function. This prevents noisy logs and reduces the risk of exposing sensitive data.

Highlights

  • Debug Message Update: The debug messages in the ActionDef.runWithTelemetry function have been modified to remove the JSON bytes of the input and output. This change aims to reduce log noise and prevent potential data exposure.
  • JSON Marshaling Removal: The code responsible for marshaling the input and output into JSON for logging purposes has been removed.
  • Improved Log Readability: By removing raw bytes from the logs, the changes enhance the readability and maintainability of the logs.

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

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 removes the logging of raw input and output data within the runWithTelemetry function. This is a beneficial change that enhances security by preventing potentially sensitive information from being exposed in logs, and also improves the readability of debug output by reducing noise. The removal of the corresponding json.Marshal calls simplifies the code. The change is well-motivated and correctly implemented.

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

Labels

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

2 participants