AVM Triage Report for owner{{owner_alias}}- {{YYYY-MM-DD}}
【免费下载链接】awesome-copilotCommunity-contributed instructions, agents, skills, and configurations to help you make the most of GitHub Copilot.项目地址: https://gitcode.com/GitHub_Trending/aw/awesome-copilot
Mode:{{quick|deep}}- {{"thread-only analysis" if quick else "full code-delta + upstream-schema + thread analysis"}}
Triage summary
Total open: {{total}} Copilot-ready now: {{unblocked}} ({{unblocked_pct}}%) - mechanical / well-specified, assignable today Copilot-ready (blocked): {{blocked}} - waiting on another in-module issue or PR Needs owner: {{H}} ({{H_pct}}%) - design, investigation, or judgement callsModule issues analysed
| Repo | Open | 🔴 High | 🟡 Medium | ⚪ Low | Copilot-ready now | Copilot-ready (blocked) | Needs owner |
|---|---|---|---|---|---|---|---|
| {{repo}} | ... | ||||||
| Total | ... |
The {{unblocked}} Copilot-ready items are the shortlist for assignment after user approval (Playbook Section 7).
All Issues - Flat List ({{total}} total)
Group issues into one tableper repo(H2 subsection per repo). Within each per-repo table, sort rows by priority descending, then by issue number ascending:
- 🔴 High
- 🟡 Medium
- ⚪ Low
Within the same priority tier, lower issue numbers come first. Do not interleave repos; finish one repo's table before starting the next. Order the repo sections themselves by total open issue count descending (largest backlog first).
Azure/{{repo}}({{open_count}} open)
| # | Title | Type | Priority | Action | Dependencies / Code surface / Upstream |
|---|---|---|---|---|---|
| #{{n}} | {{title}} | {{type}} | {{🔴/🟡/⚪}} {{priority}} | {{action}} | {{in deep mode: thread deps + code-delta evidence (overlapping files/symbols or PR diff) + upstream-schema evidence (api-version, preview flag, azurerm/azapi gap). In quick mode: thread-claimed deps only, annotate "(quick mode - code/schema not analysed)"}} |
Excluded (false positive):{{list or "none"}}
Previous-triage diff (if applicable)
- ✅Resolved since {{prev_date}}:{{list}}
- ➕New since {{prev_date}}:{{list}}
- 🔄Updated:{{list}}
- 🔁Re-opened duplicates:{{list}}
Combined Action Plan
🔴 Act now
| Repo | # | Action |
|---|---|---|
| {{repo}} | #{{n}} | {{what to do}} |
🤖 Copilot-ready batch (pending approval per issue)
| Repo | Issues |
|---|---|
| {{repo}} | #{{n}}, ...; #{{n}}(after #{{blocker}}) |
🔗 PR-in-flight - review before assigning Copilot
| Repo | Issue | Note |
|---|---|---|
| {{repo}} | #{{n}} | {{branch/PR link and rationale}} |
⚠️ Duplicates to close (after primary resolves)
| Primary | Close as dup |
|---|---|
| {{repo}} #{{primary}} | #{{dup}} |
✅ Verify-and-close (fixed upstream)
| Issue | Reason |
|---|---|
| {{repo}} #{{n}} | {{upstream fix ref and verification step}} |
📝 Document & close (draft text for approval first)
| Repo | Issues | Topic |
|---|---|---|
| {{repo}} | #{{n}}, ... | {{one-line doc topic}} |
⛓️ Ordering / "ship-together" chains
- {{chain name}}:#{{a}} → #{{b}} → #{{c}} - {{why (cite the overlapping file/symbol or blocking PR diff from Section 5 Pass 1)}}
Open questions for you
- {{question requiring owner judgment, not agent guess}}
- ...
Next steps
These issues are ready to assign to GitHub Copilot today - scope is clear, no in-module blockers, PR will run against the canonical AVM pipeline:
- #{{n}} - {{one-line scope}}
- #{{n}} + #{{n}} - {{scope}} (assign#{{primary}}, group #{{secondary}} into the same PR)
{{if any already-assigned: "#{{n}} is already assigned to Copilot."}}
**模板规则要点：** - 不要单独加"Executive Summary"章节——顶部的 Triage summary + Module issues analysed 就是摘要； - 只用三档优先级：🔴 High、🟡 Medium、⚪ Low。不允许 "Med-High" 或中间档；拿不准就向上取整为 High； - 从明细表删除 "% unblocked delegate" 列；Triage summary 里的 Copilot-ready-now 计数已经足够； - 每个模块表的列名必须与 Triage summary 的词汇一致：**Copilot-ready now**、**Copilot-ready (blocked)**、**Needs owner**，不要用 "Delegate"/"Human" 列名； - 某链节（duplicates、verify-and-close、document-close、PR-in-flight）为空时，整体省略该节而不是留空表； - 每个 Issue 引用在每个章节首次出现必须是可点击的 GitHub URL 链接；同行的后续引用用裸 `#N`； - "Ordering / ship-together chains" 与 "Open questions for you" 里**每个** `#N` 都要链接——这两节会被扫描做点击导航，不要留裸编号； - "Open questions" 只保留所有者才能做的决策（所有权、设计取舍、ping-vs-close），不询问智能体能从线程推断的内容； - 报告放在调用者指定路径；未指定则默认当前工作目录的 `./avm-triage-<owner_alias>-<YYYY-MM-DD>.md`（见 Quick Start）； - 标题下必须包含 `**Mode:**` 行，让消费者知道依赖边是证据背书（deep）还是线程声称（quick）； - "All Issues - Flat List" 每个仓库一张表（H3 小节 `Azure/{{repo}}`），表内按优先级降序（🔴 → 🟡 → ⚪）再按 Issue 号升序；仓库小节之间按开放 Issue 总数降序排列，不要合成单张表。 --- ## 十三、附录 A——AVM 机器人标签速查 | Label | 含义 | |---|---| | `Needs: Triage 🔍` | 维护者尚未审阅 | | `Status: Response Overdue 🚩` | SLA 内无响应 | | `Needs: Immediate Attention ‼️` | 进一步升级 | 解读技巧：这些标签表示 SLA 升级而非内容，处理时只概括陈旧度，不要逐条复述机器人评论。 ## 十四、附录 B——常用命令速查 ```bash # 收集开放式 Issue（专用仓库） gh issue list --repo Azure/<repo> --state open --limit 200 \ --json number,title,labels,assignees,createdAt,updatedAt # 已认证 curl 回退（先为 SSO 执行 gh auth refresh -s read:org） curl -sS -H "Authorization: Bearer $(gh auth token)" \ "https://api.github.com/repos/Azure/<repo>/issues?state=open&per_page=100" # Bicep 共享仓库 - 在正文+标题搜斜杠路径 q='repo:Azure/bicep-registry-modules is:issue is:open "avm/res/<path>"' curl -sS "https://api.github.com/search/issues?q=$(python3 -c 'import urllib.parse,sys;print(urllib.parse.quote(sys.argv[1]))' "$q")&per_page=100" # 深度阅读（Issue 正文 + 评论） gh issue view <number> --repo Azure/<repo> --comments # 或 curl -sS "https://api.github.com/repos/Azure/<repo>/issues/<number>" curl -sS "https://api.github.com/repos/Azure/<repo>/issues/<number>/comments" # 确认之前跟踪的 Issue 当前状态（关闭？重新打开？） curl -sS "https://api.github.com/repos/Azure/<repo>/issues/<number>" \ | python3 -c "import sys,json;d=json.load(sys.stdin);print(d['state'],d.get('closed_at'))" # 指派 Copilot（仅用户批准后） gh issue edit <number> --repo Azure/<repo> --add-assignee app/copilot ``` ## 十五、附录 C——认证、限流与 SSO 求生手册 **优先认证 `gh`**，始终优先于未认证 curl： ```bash # 一次性登录（打开浏览器） gh auth login -h github.com -p https -w # 为 Azure 组织授权 SAML/SSO（访问 Azure/* 仓库所需） gh auth refresh -h github.com -s read:org gh auth status # 确认 "Token scopes" 在 SSO 下包含该组织 ``` 若针对 `Azure/*` 的 `gh` 命令返回 `SAML enforcement`，打开 `gh` 打印的 URL，为 Azure SSO 会话点击 **Authorize**，然后重跑。任何有分量的 triage 运行都需要更高的已认证限流（5000 req/h）。 - **多 `gh` 账户**：`gh auth status` 显示所有已登录账户。若当前账户未获 Azure 组织 SSO 授权而另一账户已获，先 `gh auth switch --user <authorized-account>` 再收集。用 `gh issue list --repo Azure/bicep-registry-modules --limit 1` 检查——返回干净结果即确认本会话 SSO 正常。 - **已认证 curl 回退**：必须用 curl（脚本、Search API）时带上 token，以享受 5000/h 限额并访问组织门控内容： ```bash curl -sS -H "Authorization: Bearer $(gh auth token)" \ "https://api.github.com/repos/Azure/<repo>/issues?state=open&per_page=100"【免费下载链接】awesome-copilotCommunity-contributed instructions, agents, skills, and configurations to help you make the most of GitHub Copilot.项目地址: https://gitcode.com/GitHub_Trending/aw/awesome-copilot
创作声明：本文部分内容由AI辅助生成（AIGC），仅供参考
