feat(ci): add Gemini-powered GitHub Action workflows by MrOrz · Pull Request #27 · cofacts/ai

MrOrz · 2026-04-21T16:47:59Z

🚀 Pull Request: Add Gemini-powered CI/CD Automation Workflows

This PR introduces a suite of automated workflows powered by the Gemini CLI to enhance our development lifecycle. These tools are designed to streamline issue management, code reviews, and interactive assistance directly within GitHub.

🛠 Included Workflows:

🔀 Gemini Triage: Automatically suggests and applies labels to new issues based on their content.
🔎 Gemini Review: Provides automated code reviews on new Pull Requests, leveraging an MCP (Model Context Protocol) server for deep repository context.
🧙 Gemini Plan Execution: Allows authorized users to request and approve code changes directly via comments.
▶️ Gemini Invoke: A general-purpose assistant that responds to questions about code or issues when mentioned.

🔐 Security & Authentication:

Auth Alignment: These workflows are pre-configured to use our existing Workload Identity Provider and Vertex AI settings (secrets.GC_*).
Access Control: Only repository Owners, Members, or Collaborators can trigger manual commands, preventing external abuse of GCP credits.

📖 How to Use:

Simply mention @gemini-cli in any Issue or Pull Request comment:

Run a manual review: @gemini-cli /review
Re-triage an issue: @gemini-cli /triage
Execute a code fix: @gemini-cli /approve Fix the typo in agent.py
Ask a question: @gemini-cli How does the source linkage logic work?

🎯 Goal:

Our goal is to integrate more automation tools into this repository to reduce manual overhead and improve code quality. This is a significant step toward a more "AI-native" development experience.

- Add workflows for automatic triage, review, and interaction - Align GCP authentication with existing secrets (Workload Identity Provider) - Enable Vertex AI support by default Co-authored-by: Gemini CLI <gemini-cli@google.com>

github-actions · 2026-04-21T16:48:08Z

🤖 Hi @MrOrz, I've received your request, and I'm working on it now! You can track my progress in the logs for more details.

github-actions · 2026-04-21T16:48:49Z

🤖 I'm sorry @MrOrz, but I was unable to process your request. Please see the logs for more details.

gemini-code-assist

Code Review

This pull request introduces several TOML configuration files defining prompts for various Gemini-powered GitHub automation tasks, including context gathering, plan execution, code review, and issue triage. It also updates the .gitignore file to exclude Gemini-related local directories and credential files. Feedback was provided regarding a duplicated instruction step in the invocation prompt, potential shell command failures when writing JSON to environment variables due to quote escaping, and the use of redirection operators that could overwrite rather than append to the GitHub environment file.

When use_vertex_ai is true, authentication must be handled via WIF/OAuth2, and providing an API key causes a 401 conflict error. Co-authored-by: Gemini CLI <gemini-cli@google.com>

MrOrz · 2026-04-21T16:54:09Z

@gemini-cli hello can you see this? Can you see the github checks?

MrOrz · 2026-04-21T16:56:45Z

@gemini-cli hello can you see this? Can you see the github checks?

github-actions · 2026-04-21T16:56:56Z

🤖 Hi @MrOrz, I've received your request, and I'm working on it now! You can track my progress in the logs for more details.

github-actions · 2026-04-21T16:57:28Z

🤖 I'm sorry @MrOrz, but I was unable to process your request. Please see the logs for more details.

MrOrz · 2026-04-21T17:01:07Z

@gemini-cli are you able to see past failed checks / action runs triggered by this pull request and explain what happened?

github-actions · 2026-04-21T17:01:16Z

🤖 Hi @MrOrz, I've received your request, and I'm working on it now! You can track my progress in the logs for more details.

github-actions · 2026-04-21T17:02:13Z

🤖 AI Assistant: Plan of Action

I have analyzed the request and the repository history for this pull request. While I cannot directly access the raw terminal logs of past GitHub Action runs, I can reconstruct the sequence of events and explain the failures based on the commit history and the corrective measures taken.

Resource Estimate:

Estimated Tool Calls: 1
Files to Modify: 0

Proposed Steps:

Explain the Failures: I will provide a detailed response in the PR comments explaining the two primary issues that caused previous runs to fail:
1. Authentication Conflict: The initial configuration attempted to use both a Gemini API Key and Vertex AI (via Workload Identity Federation). This caused a 401 Unauthorized conflict because Vertex AI requires OAuth2/WIF authentication exclusively when enabled.
2. Model Availability & Region: A subsequent failure was related to the deployment region. The fix involved switching the gcp_location to global to ensure compatibility with the gemini-3-preview model.
Address Capability: I will clarify that while I can't "see" the logs like a human would in a browser, I can infer the root causes from the repository's state and the "fix" commits that were applied.

Please review this plan. To approve, comment @gemini-cli /approve on this issue. To make changes, comment changes needed.

MrOrz · 2026-04-21T17:03:18Z

@gemini-cli /approve

github-actions · 2026-04-21T17:03:36Z

🤖 Hi @MrOrz, I've received your request, and I'm working on it now! You can track my progress in the logs for more details.

github-actions · 2026-04-21T17:04:20Z

🕵️ Analysis of Previous Action Failures

I have analyzed the repository history and the sequence of events leading to this pull request's current state. While I cannot directly view the raw terminal logs of past runs, I can reconstruct the root causes from the corrective commits that were applied.

1. Authentication Conflict (Fixed in `222fd96`)

The initial deployment failed due to a 401 Unauthorized error. This occurred because the workflows were configured to use both a GEMINI_API_KEY and Vertex AI (via Workload Identity Federation).

Root Cause: When use_vertex_ai is enabled in the Gemini CLI, the application expects authentication to be handled exclusively via Google Cloud's OAuth2/WIF mechanism. Providing an explicit API key in this mode creates a conflict that the Vertex AI endpoint rejects.
Resolution: The API key was removed from the environment variables, allowing the CLI to correctly use the ambient credentials provided by the google-github-actions/auth step.

2. Region & Model Availability (Fixed in `e6f8f5e`)

A subsequent failure was related to the deployment region not supporting the requested model.

Root Cause: The configuration was originally set to a specific GCP region. However, the gemini-3-preview model (and some experimental features of the Gemini CLI) requires the location to be set to global to ensure proper routing to available inference clusters.
Resolution: The gcp_location was updated to global, ensuring compatibility with the preview model and regional availability.

🧠 How I "See" This

As an AI agent, I don't have a "browser" to click into your GitHub Action logs. Instead, I perform a "post-mortem" by analyzing the delta between failing and succeeding states in your codebase. I look for:

Commit Messages: Patterns like "fix auth conflict" or "switch location" are strong signals.
Code Diffs: Seeing exactly which environment variables were removed or which config strings were changed allows me to map those changes back to known error patterns in the Gemini CLI ecosystem.

My work on this analysis is now complete. Feel free to ask if you have more questions!

github-actions · 2026-04-21T17:04:24Z

✅ Task Complete

I have successfully executed the approved plan.

Summary of Changes:

Provided a detailed analysis of previous GitHub Action failures in the pull request comments.
Explained the root causes related to authentication conflicts and regional model availability.
Clarified how I reconstruct events and infer root causes from the repository's commit history and code deltas.

Pull Request:

The analysis was posted to this pull request: feat(ci): add Gemini-powered GitHub Action workflows #27

My work on this issue is now complete.

feat(ci): add Gemini-powered GitHub Action workflows

eddf6ad

- Add workflows for automatic triage, review, and interaction - Align GCP authentication with existing secrets (Workload Identity Provider) - Enable Vertex AI support by default Co-authored-by: Gemini CLI <gemini-cli@google.com>

github-actions Bot temporarily deployed to pr-27 April 21, 2026 16:48 Destroyed

gemini-code-assist Bot reviewed Apr 21, 2026

View reviewed changes

Comment thread .github/commands/gemini-invoke.toml

Comment thread .github/commands/gemini-scheduled-triage.toml

Comment thread .github/commands/gemini-scheduled-triage.toml

fix(ci): remove API keys to fix auth conflict with Vertex AI

222fd96

When use_vertex_ai is true, authentication must be handled via WIF/OAuth2, and providing an API key causes a 401 conflict error. Co-authored-by: Gemini CLI <gemini-cli@google.com>

github-actions Bot temporarily deployed to pr-27 April 21, 2026 16:52 Destroyed

fix: switch gemini-cli location to global to use gemini-3-preview

e6f8f5e

github-actions Bot temporarily deployed to pr-27 April 21, 2026 17:00 Destroyed

MrOrz self-assigned this Apr 21, 2026

MrOrz requested review from alfred141, andyy0216, nonumpa and yutin1987 April 21, 2026 17:11

MrOrz merged commit 827ecbc into master Apr 22, 2026
17 checks passed

MrOrz deleted the add-gemini-workflows branch April 22, 2026 13:04

Conversation

MrOrz commented Apr 21, 2026

🚀 Pull Request: Add Gemini-powered CI/CD Automation Workflows

🛠 Included Workflows:

🔐 Security & Authentication:

📖 How to Use:

🎯 Goal:

Uh oh!

github-actions Bot commented Apr 21, 2026

Uh oh!

github-actions Bot commented Apr 21, 2026

Uh oh!

gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

Code Review

Uh oh!

Uh oh!

Uh oh!

Uh oh!

MrOrz commented Apr 21, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

MrOrz commented Apr 21, 2026

Uh oh!

github-actions Bot commented Apr 21, 2026

Uh oh!

github-actions Bot commented Apr 21, 2026

Uh oh!

MrOrz commented Apr 21, 2026

Uh oh!

github-actions Bot commented Apr 21, 2026

Uh oh!

github-actions Bot commented Apr 21, 2026

🤖 AI Assistant: Plan of Action

Uh oh!

MrOrz commented Apr 21, 2026

Uh oh!

github-actions Bot commented Apr 21, 2026

Uh oh!

github-actions Bot commented Apr 21, 2026

🕵️ Analysis of Previous Action Failures

1. Authentication Conflict (Fixed in 222fd96)

2. Region & Model Availability (Fixed in e6f8f5e)

🧠 How I "See" This

Uh oh!

github-actions Bot commented Apr 21, 2026

✅ Task Complete

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

MrOrz commented Apr 21, 2026 •

edited

Loading

1. Authentication Conflict (Fixed in `222fd96`)

2. Region & Model Availability (Fixed in `e6f8f5e`)