Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

[aw] Android PR Reviewer is missing required tool

未关闭
#13,089 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
35/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
csharp, github-actions
领域
ci-cd, tooling

调研方向

Read .github/workflows/android-reviewer.md and the failed run linked in the issue to identify why the workflow reports the bash test harness as missing. The issue points to debug.md and .github/skills/agentic-workflows/SKILL.md as debugging guides. Done means diagnosing and fixing the reported workflow failure; the issue does not identify the specific change needed.

由索引模型根据 Issue 内容生成。

描述

agentic-workflows needs-triage
Workflow Failure

Workflow: Android PR Reviewer
Branch: main
Run: https://github.com/dotnet/android/actions/runs/38295593646

[!WARNING]
Missing Tools Reported: The agent reported missing tools during execution.

Missing Tools:

  • bash test harness: security

Alternatives:

Tool Alternative
bash test harness Reviewed the shell logic statically and against the authoritative PR diff.
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/dotnet/android/actions/runs/38295593646
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 Android PR Reviewer · copilot · 144.3 AIC · ◷

  • expires on Oct 19, 2026, 7:14 PM UTC
主要语言
C#
星标
2.1k
派生
581
平均合并
2 天 6 分钟
30 天内合并 PR
245

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 有 Pull Request 模板
  • 没有贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

dotnet/android 的其他 Issue

查看 dotnet/android 的全部 Issue

相似的 Issue

更多 C# Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。