trace: support advanced Git index semantics for same-call attribution
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
研究方向
Start by reading the implementation and lifecycle tests for same-call Git attribution, then inspect the existing normal-index behavior described in PR #3631. Add coverage for temporary indexes, intent-to-add entries, conflict resolution, replacement refs, and the temporary-index race path; the acceptance criteria define the expected results. Done means the listed cases pass and attribution matches only content newly staged by the committing Bash call.
由索引模型根據 Issue 內容生成。
描述
Context
Follow-up to #3625 and PR #3631. This scope was intentionally deferred while narrowing the PR to the normal-index foreground Claude Bash case, following maintainer review.
Scope
Support same-call attribution when Git does not use the repository's normal stage-0 index:
- honor
GIT_INDEX_FILE, includinggit commit --only <path>; - exclude intent-to-add entries that are not committed content;
- detect conflict-stage to stage-0 resolution without missing a changed path;
- read the exact object recorded by the index without being redirected by replacement refs.
Expected behavior
The pre-call and commit-time snapshots use the index Git is actually committing. Only content newly staged by that Bash call is attributed, and special index states cannot add or omit session attribution incorrectly.
Acceptance criteria
- A same-call
git commit --only <path>receives the correct session trailer. - Pre-existing normal-index content is not claimed by a temporary-index commit.
- Intent-to-add paths do not receive attribution unless committed.
- Resolving an unmerged path changes the index signature even when stage 0 reuses an existing blob.
- Indexed blob reads remain exact in repositories with
refs/replace/*. - Race-enabled lifecycle tests cover the temporary-index commit path.
- 主要語言
- Go
- 星號
- 582
- 分支
- 61
- 平均合併
- 12 小時 47 分鐘
- 30 天內合併 PR
- 137
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 沒有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
chainloop-dev/chainloop 的其他 Issue
-
feature-parity trace-provider
難度 2/5 1-3 小時 新手友好度 70/100
chainloop-dev/chainloop#3802 ·
維護者通常 1 天內回覆
-
bug trace-provider
難度 4/5 3-5 天 新手友好度 48/100
chainloop-dev/chainloop#3803 ·
維護者通常 1 天內回覆
-
feat(trace): support GitHub Copilot (CLI and VS Code) in Chainloop Trace可能已有人在做 @migmartri 今天認領。 未關閉Feature spec trace-provider
chainloop-dev/chainloop#3800 · 1 則留言 · 已指派 1 人 ·
維護者通常 1 天內回覆
-
Allow enabling policy enforcement at the workflow contract level可能已有人在做 @migmartri 於 10 天前認領。 未關閉component/backend new-policy spec
chainloop-dev/chainloop#3762 · 1 則留言 · 已指派 1 人 ·
維護者通常 1 天內回覆
-
chainloop component/CLI performance trace-provider
難度 4/5 3-5 天 新手友好度 62/100
chainloop-dev/chainloop#3756 ·
維護者通常 1 天內回覆
查看 chainloop-dev/chainloop 的全部 Issue
相似的 Issue
-
GitHub webhook is not subscribed to release events, so `event: release` never triggers可能已有人在做 @qsun 今天認領。 未關閉
難度 2/5 1-3 小時 新手友好度 78/100
woodpecker-ci/woodpecker#7542 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 74/100
zilliztech/milvus-backup#1386 ·
維護者通常 1 天內回覆
-
Pipelined flush no longer observes kill signals after #2042: flush backoffer is built with nil vars未關閉
難度 2/5 1-3 小時 新手友好度 78/100
維護者通常 1 天內回覆
-
model:sonnet runtime:claude security size:S
難度 2/5 1-3 小時 新手友好度 78/100
FootprintAI/Containarium#3624 · 1 則留言 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 86/100
維護者通常 1 天內回覆