Pull request template for Go

[ryanaiagent]

Pull request template for Go similar to the template used in adk-python

[gemini-code-assist]

Summary of Changes

Hello @ryanaiagent, 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 establishes a foundational pull request template for the repository, mirroring a similar structure used in adk-python. The primary goal is to streamline the submission and review process for future contributions by providing clear guidelines and required information, ensuring consistency and completeness across all incoming changes.

Highlights

• New Pull Request Template: A new pull request template has been introduced for the repository, located at .github/pull_request_template.md.
• Standardized Contribution Process: The template aims to standardize the contribution process by guiding contributors to link issues, describe changes, detail testing plans (unit and E2E), and complete a comprehensive checklist.
• Go-specific Testing Guidance: The template includes specific sections for Go unit test results and manual end-to-end testing instructions, tailored for the Go ecosystem.

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

Changelog

• .github/pull_request_template.md
  • Added a new pull request template to standardize contribution guidelines.
  • Included sections for linking issues, describing problems and solutions, and detailing testing plans.
  • Incorporated a comprehensive checklist covering documentation, self-review, testing, and dependency management.

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 a new template for Go pull requests, which is based on the one used for adk-python. The template is well-structured and covers all the necessary sections like linking to an issue, describing the change, testing plan, and a checklist. I have a couple of suggestions to improve it further. One is to use a relative link for the CONTRIBUTING.md file to make it branch-agnostic. The other is to add a newline at the end of the file, which is a common convention.

[verdverm]

Do you have an Ai policy yet? Would be good to link that directly, next to the CONTRIBUTING.md

If not, a TODO would be good if you agree it's useful to add to the list at the end

The hope is that the growing clawd spam on GitHub will read it and see if they are allowed before attempting a PR, and make sure it is easily available at their most common touch points with repos.

[verdverm]

side note, it's unclear to me if @ryanaiagent is a real person or a bot run by a maintainer, it appears to have elevated permissions for the repo, the handle implies automation

[ryanaiagent]

Hi @verdverm, No we don't have a specific AI policy yet for the repos.

[foxfrikses]

I'm planning to approve it after the two small comments are fixed.

[ryanaiagent]

Hey @foxfrikses , I have done the necessary changes. Let me know if you need anything else.