Skip to content

Fix linter issues on main#425

Open
ormergi wants to merge 1 commit into
openperouter:mainfrom
ormergi:linter-issues-fix-main
Open

Fix linter issues on main#425
ormergi wants to merge 1 commit into
openperouter:mainfrom
ormergi:linter-issues-fix-main

Conversation

@ormergi
Copy link
Copy Markdown
Contributor

@ormergi ormergi commented May 17, 2026

Is this a BUG FIX or a FEATURE ?:

Uncomment only one, leave it on its own line:

/kind bug
/kind cleanup
/kind feature
/kind design
/kind flake
/kind failing
/kind documentation
/kind regression
/kind example

What this PR does / why we need it:

Running 'make lint' on local environment fail on main branch.

This PR resolve the linter issues.

Special notes for your reviewer:
Its not clear how the these un-formatted changes slipped in.

One gap I see is CI using golnagci-lint Github Action while for local development we have 'make lint'.
Although using linter GH Action continent the local development workflow may diverge, as in this case.
We should consider have CI run make lint as well.

Release note:

NONE

AI Guidelines Acknowledgment:

  • I have reviewed all changes in this PR, including any AI-generated content, and I take full responsibility for its accuracy and correctness.

Signed-off-by: Or Mergi <ormergi@redhat.com>
@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello, 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 addresses formatting inconsistencies that were causing the local 'make lint' command to fail on the main branch. The changes ensure that the codebase adheres to the expected style guidelines, improving consistency across the project.

Highlights

  • Code Formatting: Adjusted alignment and spacing in test struct definitions to satisfy linter requirements.
New Features

🧠 You can now enable Memory (public preview) 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 the 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 counterproductive. 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.

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
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 updates the formatting of test structs in internal/conversion/validate_passthrough_test.go by realigning fields for better readability. I have no feedback to provide as there were no review comments.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant