Feat/triage labelling bot

[D-sense]

This PR adds an automatic issue triaging and labeling bot for the ADK Go repository, implemented in Go using the ADK framework.
It automatically analyzes GitHub issues and assigns appropriate labels and owners based on the issue content.

Issue Number: #287

[gemini-code-assist]

Summary of Changes

Hello @D-sense, 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 introduces a new, intelligent issue triaging and labeling bot for the ADK Go repository. By integrating with Google's Gemini model and the ADK framework, the bot automates the process of categorizing GitHub issues, assigning labels, and delegating ownership. This significantly streamlines issue management, ensuring that new issues are quickly and accurately routed to the correct teams or individuals, thereby enhancing workflow efficiency and responsiveness.

Highlights

• Automated Issue Triage: Introduces a bot to automatically triage and label GitHub issues for the ADK Go repository.
• Go ADK Framework Implementation: The bot is built in Go, leveraging the ADK (Agent Development Kit) framework for its agent functionality.
• Gemini Model Integration: Utilizes Google's Gemini model for intelligent analysis of issue content to determine appropriate labels and owners.
• Dynamic Labeling and Ownership: Automatically assigns appropriate labels and owners based on issue content and predefined rules, enhancing issue routing.
• Issue Type Modification: Capable of changing issue types (e.g., 'Bug' or 'Feature') as needed, based on the issue's content.
• Flexible Processing Modes: Supports processing individual issues (on open/reopen events) and batches of unlabeled issues via a scheduled event.
• GitHub Actions Integration: Configured for automated execution via GitHub Actions, ensuring continuous and hands-off operation.

Ignored Files

• Ignored by pattern: .github/workflows/** (1)
  • .github/workflows/triage.yml

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 triaging and labeling bot, which is a great addition. The implementation is solid, but I've found a few areas for improvement, including a critical bug in handling API responses, a configuration mismatch in the documentation that would break the GitHub Action, and several opportunities to enhance code robustness, configurability, and maintainability. Please see my detailed comments.

[D-sense]

Are we keeping the same list for those?

[karolpiotrowicz]

The list will be different. Something we need to agree on first internally.

[D-sense]

@karolpiotrowicz that sounds very good! Once you have a decision/conclusion I would update it.

[D-sense]

This is good for a review when someone gets a chance.
Thanks!