Close the loop: notify reporters when a fix ships (version + channel)

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

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
3/5
預估耗時
半天
新手友好度
65/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
bash, github
領域
release

研究方向

Start from scripts/sync-labels.sh as the model for the new scripts/notify-fixed.sh, and read the current CHANGELOG's "Fixed" section to see how entries cite issues. Find where the repo's script tests live so the missing-citation check has a home. Done means a dry-run over the last release prints one comment per referenced issue, the test fails when a Fixed entry cites no issue, and docs/labels.md documents the workflow.

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

描述

area: ci priority: 3 low status: confirmed type: feature

Roadmap item (tracking: #289). From a read-only code audit at main (9c32731); key claims re-checked in code where marked verified. [INFERENCE] = not observed at runtime.

Problem

Nothing comments on issues at release time (no gh issue comment in scripts/workflows); Fixes #N closes at merge, before the alpha ships, without saying which version to run. "What's new" (apps/desktop/src/lib/updates.ts) does not link fixed issues.

Proposal

Maintainer-run scripts/notify-fixed.sh (like sync-labels.sh, no bot): read the new CHANGELOG "Fixed" section, comment "Fixed in vX (alpha) — run atlas update" on each referenced issue; test that Fixed entries cite an issue.

Acceptance

  • Dry-run on the last release prints one comment per referenced issue; missing citation fails the test; documented in docs/labels.md.
主要語言
Rust
星號
3
分支
1
平均合併
9 小時 51 分鐘
30 天內合併 PR
310

環境準備

從這裡開始

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

codeatlasdev/atlas 的其他 Issue

查看 codeatlasdev/atlas 的全部 Issue

相似的 Issue

更多 Rust Issue

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

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