all: run golangci-lint fmt happy

[zchee]

Format import section

$ go run github.com/golangci/golangci-lint/v2/cmd/golangci-lint@latest fmt

[gemini-code-assist]

Summary of Changes

Hello @zchee, I'm Gemini Code Assist¹! 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 integrates gofumpt into the golangci-lint configuration, standardizing code formatting across the Go codebase. The changes primarily involve updating the .golangci.yml file with new formatter settings and applying these new formatting rules, particularly to import statements, across a wide range of Go source files. Additionally, it includes several minor code style refinements and corrections to ensure better consistency and readability.

Highlights

• Code Formatting Enforcement: The golangci-lint configuration has been updated to include gofumpt as an enabled formatter, alongside goimports. This introduces stricter and more opinionated formatting rules for Go code.
• Formatter Settings: Specific settings have been added for both goimports and gofumpt within the .golangci.yml file. goimports now uses google.golang.org/adk as a local prefix, and gofumpt is configured with extra-rules: true and a module-path.
• Import Statement Reordering: Numerous Go files across the repository have had their import statements reordered and grouped to comply with the new gofumpt and goimports rules, ensuring consistent import block formatting.
• Code Style and Readability Improvements: Minor code style adjustments were made, including grouping multiple var _ Interface = (*Struct)(nil) declarations into single var (...) blocks, simplifying function signatures (e.g., args map[string]any, result map[string]any to args, result map[string]any), and removing extraneous blank lines.
• Octal Literal Correction: File permission octal literals used in os.WriteFile calls were updated from 0600 to 0o600 and 0666 to 0o666 for explicit octal representation.
• Explicit Return Statements: Return statements in ExtractStateDeltas and extractStateDeltas functions were made explicit to improve clarity.

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

[gemini-code-assist]

Code Review

This pull request introduces gofumpt for code formatting and applies its rules across the codebase. The changes primarily consist of import reordering, parameter grouping, and other stylistic improvements that enhance code consistency and readability. The configuration in .golangci.yml looks correct. Overall, this is a great step towards maintaining a consistent code style. I've added a few comments to highlight some of the beneficial changes.

[dpasiukevich]

One small nit and we can merge.

Thanks for the PR!

[zchee]

@dpasiukevich Fixed. PTAL.

[zchee]

@dpasiukevich Resolve conflict. PTALA.

[dpasiukevich]

Thanks!