run-gemini-cli: Run Gemini CLI in GitHub Actions

Overview

run-gemini-cli is a GitHub Action that runs the Gemini CLI in repository workflows. It lets teams assign routine coding work to an agent or request assistance in issue and pull request comments, rather than running the CLI only from a developer's terminal.

It makes sense for teams already using GitHub Actions that want to automate review or triage, or provide an on-demand coding assistant. Workflows and authentication are configurable, with options for Gemini API access or Google Cloud and GitHub credentials.

Key Features

• Run Gemini CLI in response to repository events or scheduled workflows.
• Request work by mentioning @gemini-cli in issue or pull request comments.
• Use provided workflow examples for dispatch, issue triage, pull request review, and assistant tasks.
• Configure the prompt, model, CLI version, settings, and extensions through action inputs.
• Authenticate to Gemini through an API key, Google Cloud, Vertex AI, or Gemini Code Assist options.
• Use the workflow's GITHUB_TOKEN or configure a custom GitHub App for GitHub access.
• Optionally send telemetry to a Google Cloud project and upload execution artifacts.

Use Cases

• A maintainer can request automated pull request reviews when changes are opened or with a comment command.
• A repository team can triage new issues automatically or on a schedule, reducing manual sorting.
• A developer can ask for explanations, debugging help, tests, or code changes directly from an issue or pull request.
• A platform team can standardize Gemini CLI access across repositories using reusable GitHub Actions workflows and shared configuration.

Getting Started

Store a Gemini API key as the GEMINI_API_KEY repository secret, then use the Gemini CLI /setup-github command to create workflows, or copy an example workflow into .github/workflows. See the README for setup details and authentication options.

Alternatives

• gh-aw: gh-aw defines agentic workflows in Markdown and compiles them into GitHub Actions, rather than running Gemini CLI directly.
• ai-outfitter/actions: ai-outfitter/actions runs Outfitter profiles as scheduled or event-driven GitHub Actions, rather than integrating Gemini CLI.
• Ferry: Ferry turns Jira column moves into reviewed draft pull requests, rather than offering a Gemini CLI for general issue and PR tasks.

Considerations

• This requires a GitHub Actions workflow and credentials for both Gemini services and GitHub API access. Choose and configure an authentication method before enabling workflows.
• Workflows that can modify code or act on issues and pull requests need carefully scoped permissions. The project recommends reviewing its best practices and pinning action versions.
• Gemini CLI requests can incur service usage, and behavior depends on the selected model, credentials, and workflow configuration.
• The README provides example workflows to copy and customize, rather than describing a one-size-fits-all workflow setup.