Run Google Gemini in GitHub Actions with gh-aw

Google Gemini is Google’s model family for coding and repository analysis. gh-aw runs Gemini inside GitHub Actions from a Markdown workflow and adds GitHub event triggers, sandboxing controls, and safe outputs so automated repository work can stay constrained and reviewable.

Setup

Set engine: gemini and provide GEMINI_API_KEY, or configure keyless authentication with Google Workload Identity Federation. See Gemini authentication for the available setup paths.

Initialize the repository

Run gh aw init --engine gemini to configure the repository. The --engine gemini flag skips Copilot-specific files (MCP server configuration, Copilot dispatcher skill) and writes only the files useful for any engine: .gitattributes, VS Code settings, and the custom agent file.

gh aw init --engine gemini

---
on:
  schedule: daily

permissions:
  contents: read
  issues: read
  pull-requests: read

engine: gemini

safe-outputs:
  create-issue:
    title-prefix: "[status] "
    labels: [report]
    close-older-issues: true
---

# Daily Repository Status

Analyze the repository and create a concise daily status report covering:
- Open issues and their priority
- Recent PR activity
- Upcoming work items

When to choose gh-aw vs. running Gemini directly in Actions

Choose gh-aw when the workflow should be authored in Markdown, share one structure across engines, and restrict GitHub writes to validated safe outputs. Run Gemini directly in Actions when the job needs a custom script pipeline and all security and review controls are managed manually.