Skip to content

fix: preserve GitHubID in carryForwardComment to prevent duplicate PR comments#340

Merged
tomasz-tomczyk merged 1 commit intomainfrom
fix/314-carryforward-drops-githubid
Apr 24, 2026
Merged

fix: preserve GitHubID in carryForwardComment to prevent duplicate PR comments#340
tomasz-tomczyk merged 1 commit intomainfrom
fix/314-carryforward-drops-githubid

Conversation

@tomasz-tomczyk
Copy link
Copy Markdown
Owner

Summary

  • carryForwardComment() in watch.go was missing GitHubID field when constructing the carried-forward comment
  • This caused GitHub PR comments (fetched via crit pull) to lose their GitHubID after a round-complete, making crit push treat them as new comments and post duplicates

Closes #314

Review

  • Code review: passed (go-expert fresh review, all 19 Comment fields verified mapped)
  • Parity audit: N/A (backend-only change)

Test plan

  • New test: TestCarryForwardComment_PreservesGitHubID in watch_test.go
  • Updated existing TestCarryForwardComment in session_test.go to cover GitHubID
  • Full test suite passes with -race flag

🤖 Generated with Claude Code

… comments

carryForwardComment was copying all Comment fields except GitHubID, so
comments pulled from GitHub via `crit pull` lost their GitHub identity
after round-complete. This caused `crit push` to treat them as new
comments and post duplicates.

Fixes #314

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@tomasz-tomczyk tomasz-tomczyk merged commit 5522c7a into main Apr 24, 2026
4 checks passed
@tomasz-tomczyk tomasz-tomczyk deleted the fix/314-carryforward-drops-githubid branch April 24, 2026 07:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

bug: carryForwardComment drops GitHubID — causes duplicate PR comments after round-complete

1 participant