mirror of
https://github.com/encounter/adk-python.git
synced 2026-07-09 18:19:28 -07:00
67 lines
3.5 KiB
Markdown
67 lines
3.5 KiB
Markdown
 
|
# ADK Issue Triaging Assistant
|
||
|
|
|
||
|
|
The ADK Issue Triaging Assistant is a Python-based agent designed to help manage and triage GitHub issues for the `google/adk-python` repository. It uses a large language model to analyze new and unlabelled issues, recommend appropriate labels based on a predefined set of rules, and apply them.
|
||
|
|
|
||
|
|
This agent can be operated in two distinct modes: an interactive mode for local use or as a fully automated GitHub Actions workflow.
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
## Interactive Mode
|
||
|
|
|
||
|
|
This mode allows you to run the agent locally to review its recommendations in real-time before any changes are made to your repository's issues.
|
||
|
|
|
||
|
|
### Features
|
||
|
|
* **Web Interface**: The agent's interactive mode can be rendered in a web browser using the ADK's `adk web` command.
|
||
|
|
* **User Approval**: In interactive mode, the agent is instructed to ask for your confirmation before applying a label to a GitHub issue.
|
||
|
|
|
||
|
|
### Running in Interactive Mode
|
||
|
|
To run the agent in interactive mode, first set the required environment variables. Then, execute the following command in your terminal:
|
||
|
|
|
||
|
|
```bash
|
||
|
|
adk web
|
||
|
|
```
|
||
|
|
This will start a local server and provide a URL to access the agent's web interface in your browser.
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
## GitHub Workflow Mode
|
||
|
|
|
||
|
|
For automated, hands-off issue triaging, the agent can be integrated directly into your repository's CI/CD pipeline using a GitHub Actions workflow.
|
||
|
|
|
||
|
|
### Workflow Triggers
|
||
|
|
The GitHub workflow is configured to run on specific triggers:
|
||
|
|
|
||
|
|
1. **Issue Events**: The workflow executes automatically whenever a new issue is `opened` or an existing one is `reopened`.
|
||
|
|
|
||
|
|
2. **Scheduled Runs**: The workflow also runs on a recurring schedule (every 6 hours) to process any unlabelled issues that may have been missed.
|
||
|
|
|
||
|
|
### Automated Labeling
|
||
|
|
When running as part of the GitHub workflow, the agent operates non-interactively. It identifies the best label and applies it directly without requiring user approval. This behavior is configured by setting the `INTERACTIVE` environment variable to `0` in the workflow file.
|
||
|
|
|
||
|
|
### Workflow Configuration
|
||
|
|
The workflow is defined in a YAML file (`.github/workflows/triage.yml`). This file contains the steps to check out the code, set up the Python environment, install dependencies, and run the triaging script with the necessary environment variables and secrets.
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
## Setup and Configuration
|
||
|
|
|
||
|
|
Whether running in interactive or workflow mode, the agent requires the following setup.
|
||
|
|
|
||
|
|
### Dependencies
|
||
|
|
The agent requires the following Python libraries.
|
||
|
|
|
||
|
|
```bash
|
||
|
|
pip install --upgrade pip
|
||
|
|
pip install google-adk requests
|
||
|
|
```
|
||
|
|
|
||
|
|
### Environment Variables
|
||
|
|
The following environment variables are required for the agent to connect to the necessary services.
|
||
|
|
|
||
|
|
* `GITHUB_TOKEN`: **(Required)** A GitHub Personal Access Token with `issues:write` permissions. Needed for both interactive and workflow modes.
|
||
|
|
* `GOOGLE_API_KEY`: **(Required)** Your API key for the Gemini API. Needed for both interactive and workflow modes.
|
||
|
|
* `OWNER`: The GitHub organization or username that owns the repository (e.g., `google`). Needed for both modes.
|
||
|
|
* `REPO`: The name of the GitHub repository (e.g., `adk-python`). Needed for both modes.
|
||
|
|
* `INTERACTIVE`: Controls the agent's interaction mode. For the automated workflow, this is set to `0`. For interactive mode, it should be set to `1` or left unset.
|
||
|
|
|
||
|
|
For local execution in interactive mode, you can place these variables in a `.env` file in the project's root directory. For the GitHub workflow, they should be configured as repository secrets.
|