Conversation
Add smoke-gemini workflow based on smoke-copilot pattern to validate the Gemini engine. Tests GitHub MCP connectivity, github.com reachability, file write/read, and safe-outputs invocation. Requires GEMINI_API_KEY secret to be configured in the repository. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This comment has been minimized.
This comment has been minimized.
🔥 Smoke Test: Copilot BYOK (Offline) Mode
Running in BYOK offline mode ( Overall: PASS — @lpcox (no assignees)
|
|
Smoke Test Results
|
|
Smoke test report:
Warning The following domain was blocked by the firewall during workflow execution:
To allow these domains, add them to the network:
allowed:
- defaults
- "registry.npmjs.org"See Network Configuration for more information.
|
🏗️ Build Test Suite Results
Overall: 0/8 ecosystems passed — ❌ FAIL Error DetailsAll The workflow's gh CLI proxy only permits access to
|
There was a problem hiding this comment.
Pull request overview
Adds a new agentic workflow to smoke-test the Gemini engine in this repo’s Agentic Workflows Firewall setup, following the existing smoke workflow patterns (pre-step data collection + agent execution + safe-outputs enforcement).
Changes:
- Introduces a new
smoke-geminiworkflow definition (.md) for scheduled/PR-triggered Gemini engine validation. - Adds the compiled workflow lockfile (
.lock.yml) generated from the markdown source.
Show a summary per file
| File | Description |
|---|---|
| .github/workflows/smoke-gemini.md | New Gemini smoke-test workflow definition: pre-compute checks, prompt instructions, safe-outputs validation. |
| .github/workflows/smoke-gemini.lock.yml | Compiled lock workflow generated from the markdown source for execution in GitHub Actions. |
Copilot's findings
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 2/2 changed files
- Comments generated: 1
| issues: read | ||
| actions: read | ||
| name: Smoke Gemini | ||
| engine: gemini |
There was a problem hiding this comment.
This workflow doesn’t pin the MCP gateway version in frontmatter (unlike smoke-copilot), so the compiled lock ends up using gh-aw-mcpg v0.2.26. If the goal is to mirror smoke-copilot / stay on the newer gateway, add sandbox.mcp.version: v0.2.29 (or the repo’s current standard) and re-run gh aw compile to refresh the lock file.
| engine: gemini | |
| engine: gemini | |
| sandbox: | |
| mcp: | |
| version: v0.2.29 |
Smoke Test Results: GitHub Actions Services Connectivity
All checks failed.
|
🔬 Copilot Smoke Test Results
Overall: FAIL — pre-computed step outputs were not injected ( Author: @lpcox | Assignees: none
|
Summary
Adds a new
smoke-geminiagentic workflow to validate the Gemini engine, mirroring the existingsmoke-copilotpattern.What it tests
github-list_pull_requestsadd_commentwas invoked on PR triggersConfiguration
geminiGEMINI_API_KEY(Google Gemini API key)smoke-geminiSecurity review (safe-update)
GEMINI_API_KEY— Google Gemini API key for inference. Used only within the AWF sandbox; not exposed to untrusted code.