PlanningItem evidence: git commits, checked against the history

已关闭
  • 哪里不对？
#455 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
git, rust, yaml
领域
devtools

调研方向

Start by reading the PlanningItem step and evidence handling described in issue #436, then trace the validator and the steps --json, context, log, and changes entry points. The issue defines the proposed commit evidence syntax and validation outcomes, but leaves the policy and command integration scope open. Done means commit hashes are validated against repository history and exposed in the requested outputs and filters.

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

描述

Problem

PlanningItems now have structured steps (#436) and evidence: (ref: to an element, path: to a file). For work tracking the most useful evidence of a done step is often the commit(s) that delivered it, together with the test cases made active. Today a commit can only be written in the body, so it is not checked (a typo or a rebased-away hash goes unnoticed) and not queryable ("which commits delivered PI-X?").

Proposal

  • evidence: - commit: <sha> (abbreviated ≥ 7 hex accepted), resolved against the repository's git history by validate: unknown or ambiguous hash → finding; optional check that the commit touches a path the step's elements name.
  • steps --json / context include the commits; log/changes can filter by planning item.
  • Policy option: a leaf done item must have at least one commit evidence (in addition to E719's element/path evidence).
主要语言
Rust
星标
8
派生
1
平均合并
3 小时 35 分钟
30 天内合并 PR
69

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。

从这里开始

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

sjames/syscribe 的其他 Issue

查看 sjames/syscribe 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

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