| … | … | @@ -1337,31 +1337,109 @@ export const makeVcsDriverShape = Effect.fn("makeGitVcsDriverShape")(function* ( | |
| 1402 | + | previousByRef.set(entry.ref, entry.commit); | |
| 1403 | + | if (entry.ref === "HEAD") return []; | |
| 1404 | + | if (entry.updatedAt < since || entry.subject === "update by push") return []; | |
| 1405 | + | return [entry.commit, ...(previous === undefined ? [] : [`^${previous}`])]; | |
🟠 High vcs/GitVcsDriver.ts:1405
When a remote advances from A to B to C after the checkpoint, git rev-list excludes B because the later ^B range subtracts it from the combined result. B then remains in ownCommits, so files changed only by that fetched commit are incorrectly reported as agent-authored. Avoid adding each previous tip as a global exclusion, or evaluate the fetch ranges independently.
🤖 Copy this AI Prompt to have your agent fix this:
| 1 | In file @apps/server/src/vcs/GitVcsDriver.ts around line 1405: |
| 2 | |
| 3 | When a remote advances from `A` to `B` to `C` after the checkpoint, `git rev-list` excludes `B` because the later `^B` range subtracts it from the combined result. `B` then remains in `ownCommits`, so files changed only by that fetched commit are incorrectly reported as agent-authored. Avoid adding each previous tip as a global exclusion, or evaluate the fetch ranges independently. |
Fixed in 67686b3: each fetch range now runs as its own rev-list walk, so a later ^previous can't hide commits an earlier fetch delivered. "leaves out every upstream commit when several fetches advance a remote" covers the A→B→C case and fails on the previous commit. Also, CI is still waiting on workflow approval for this fork PR, if a maintainer can approve the run.
Sorry, I'm unable to act on this request because you do not have permissions within this repository.