Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

[aw] Rig Skill Integration - Gemini failed

未關閉
#605 1 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
3/5
預估耗時
1-3 小時
新手友好度
22/100
Issue 類型
缺陷
描述清晰度
需要釐清
活躍度
活躍
技術堆疊
github-actions
領域
ci-cd

研究方向

The failing workflow is .github/workflows/rig-skill-integration-gemini.md, and the failed run is linked in the issue body. The report names only the secret verification step and the category secret_verification_failed, without saying which secret is missing. Start by reading the workflow's secret checks and the linked run log to identify the missing secret. Done means the run's secret validation passes, which may need repository settings access that a newcomer may not have.

由索引模型根據 Issue 內容生成。

描述

agentic-workflows
Workflow Failure

Workflow: Rig Skill Integration - Gemini
Branch: main
Run: https://github.com/githubnext/rig/actions/runs/37948264558

[!WARNING]
Secret Verification Failed: The workflow's secret validation step failed. Please check that the required secrets are configured in your repository settings.

For more information on configuring tokens, see: https://github.github.com/gh-aw/reference/engines/

Action Required

Assign this issue to an agent to debug and fix the issue.

Debug with any coding agent

Use this prompt with any coding agent (GitHub Copilot, Claude, Gemini, etc.):

Debug the agentic workflow failure using https://raw.githubusercontent.com/github/gh-aw/main/debug.md

The failed workflow run is at https://github.com/githubnext/rig/actions/runs/37948264558
Manually invoke the agent

Debug this workflow failure using your favorite Agent CLI and the agentic-workflows prompt.

[!TIP]

Stop reporting this workflow as a failure

To stop a workflow from creating failure issues, set report-failure-as-issue: false in its frontmatter:

safe-outputs:
  report-failure-as-issue: false

Generated from Rig Skill Integration - Gemini · ◷

  • expires on Oct 16, 2026, 2:59 PM UTC
主要語言
TypeScript
星號
14
分支
0
平均合併
3 小時 38 分鐘
30 天內合併 PR
29

環境準備

這個專案沒有提供開發容器、Dockerfile 或貢獻指南,環境需要你自己搭建:先看它的 README,通用步驟見我們的新手貢獻指南。

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

githubnext/rig 的其他 Issue

查看 githubnext/rig 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。