Repository navigation
Commit 1db2c6e
test: assert summary updates target the created comment id
The fake github already records both the id returned by createComment
and the comment_id passed to each updateComment, but no test
cross-referenced them. The orchestrator stores the id in a single
closure variable (summaryCommentId) and reuses it, so confusion is
unlikely — but a refactor that bound the wrong value (e.g. the PR
number from the same scope) would slip through every existing test.
The user-visible regression: initial 'is backporting…' placeholder
never updates, users see a stale orphan comment for the rest of the
run. One assertion in the happy-path summary test catches it without
adding a dedicated test or duplicating setup.
Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>1 parent 716c6c8 commit 1db2c6e
1 file changed
Lines changed: 7 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
697 | 697 | | |
698 | 698 | | |
699 | 699 | | |
| 700 | + | |
| 701 | + | |
| 702 | + | |
| 703 | + | |
| 704 | + | |
| 705 | + | |
| 706 | + | |
700 | 707 | | |
701 | 708 | | |
702 | 709 | | |
| |||
0 commit comments