fix(ci): duplicate comments prevented via issue id deduplication#3449
Merged
FabianKramm merged 1 commit intomainfrom Jan 9, 2026
Merged
fix(ci): duplicate comments prevented via issue id deduplication#3449FabianKramm merged 1 commit intomainfrom
FabianKramm merged 1 commit intomainfrom
Conversation
Linear sync created duplicate comments on issues when same ID appeared in both PR body and branch name. Example: ENG-8061 got two identical "Now available in stable release v0.30.4" comments 1 second apart. Root cause: IssueIDs() extracted from both PR body AND branch name, returning duplicates when both contained the same issue reference. This was exposed by commit e480400 which added stable release comments for already-released issues - before that, duplicates were silently skipped because issue was already in "Released" state. Resolves OPS-460
sydorovdmytro
approved these changes
Jan 8, 2026
loft-bot
pushed a commit
that referenced
this pull request
Jan 9, 2026
Linear sync created duplicate comments on issues when same ID appeared in both PR body and branch name. Example: ENG-8061 got two identical "Now available in stable release v0.30.4" comments 1 second apart. Root cause: IssueIDs() extracted from both PR body AND branch name, returning duplicates when both contained the same issue reference. This was exposed by commit e480400 which added stable release comments for already-released issues - before that, duplicates were silently skipped because issue was already in "Released" state. Resolves OPS-460 (cherry picked from commit cfcf45a) # Conflicts: # hack/linear-sync/main.go # hack/linear-sync/main_test.go
loft-bot
pushed a commit
that referenced
this pull request
Jan 9, 2026
Linear sync created duplicate comments on issues when same ID appeared in both PR body and branch name. Example: ENG-8061 got two identical "Now available in stable release v0.30.4" comments 1 second apart. Root cause: IssueIDs() extracted from both PR body AND branch name, returning duplicates when both contained the same issue reference. This was exposed by commit e480400 which added stable release comments for already-released issues - before that, duplicates were silently skipped because issue was already in "Released" state. Resolves OPS-460 (cherry picked from commit cfcf45a) # Conflicts: # hack/linear-sync/main.go # hack/linear-sync/main_test.go
loft-bot
pushed a commit
that referenced
this pull request
Jan 9, 2026
Linear sync created duplicate comments on issues when same ID appeared in both PR body and branch name. Example: ENG-8061 got two identical "Now available in stable release v0.30.4" comments 1 second apart. Root cause: IssueIDs() extracted from both PR body AND branch name, returning duplicates when both contained the same issue reference. This was exposed by commit e480400 which added stable release comments for already-released issues - before that, duplicates were silently skipped because issue was already in "Released" state. Resolves OPS-460 (cherry picked from commit cfcf45a)
loft-bot
pushed a commit
that referenced
this pull request
Jan 9, 2026
Linear sync created duplicate comments on issues when same ID appeared in both PR body and branch name. Example: ENG-8061 got two identical "Now available in stable release v0.30.4" comments 1 second apart. Root cause: IssueIDs() extracted from both PR body AND branch name, returning duplicates when both contained the same issue reference. This was exposed by commit e480400 which added stable release comments for already-released issues - before that, duplicates were silently skipped because issue was already in "Released" state. Resolves OPS-460 (cherry picked from commit cfcf45a)
loft-bot
pushed a commit
that referenced
this pull request
Jan 9, 2026
Linear sync created duplicate comments on issues when same ID appeared in both PR body and branch name. Example: ENG-8061 got two identical "Now available in stable release v0.30.4" comments 1 second apart. Root cause: IssueIDs() extracted from both PR body AND branch name, returning duplicates when both contained the same issue reference. This was exposed by commit e480400 which added stable release comments for already-released issues - before that, duplicates were silently skipped because issue was already in "Released" state. Resolves OPS-460 (cherry picked from commit cfcf45a)
Contributor
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation and see the Github Action logs for details |
Piotr1215
added a commit
that referenced
this pull request
Jan 9, 2026
…) (#3455) Linear sync created duplicate comments on issues when same ID appeared in both PR body and branch name. Example: ENG-8061 got two identical "Now available in stable release v0.30.4" comments 1 second apart. Root cause: IssueIDs() extracted from both PR body AND branch name, returning duplicates when both contained the same issue reference. This was exposed by commit e480400 which added stable release comments for already-released issues - before that, duplicates were silently skipped because issue was already in "Released" state. Resolves OPS-460 (cherry picked from commit cfcf45a) # Conflicts: # hack/linear-sync/main.go # hack/linear-sync/main_test.go Co-authored-by: Piotr <piotr.zaniewski@loft.sh>
Piotr1215
added a commit
that referenced
this pull request
Jan 9, 2026
…) (#3456) Linear sync created duplicate comments on issues when same ID appeared in both PR body and branch name. Example: ENG-8061 got two identical "Now available in stable release v0.30.4" comments 1 second apart. Root cause: IssueIDs() extracted from both PR body AND branch name, returning duplicates when both contained the same issue reference. This was exposed by commit e480400 which added stable release comments for already-released issues - before that, duplicates were silently skipped because issue was already in "Released" state. Resolves OPS-460 (cherry picked from commit cfcf45a) # Conflicts: # hack/linear-sync/main.go # hack/linear-sync/main_test.go Co-authored-by: Piotr <piotr.zaniewski@loft.sh>
Piotr1215
added a commit
that referenced
this pull request
Jan 9, 2026
…) (#3457) Linear sync created duplicate comments on issues when same ID appeared in both PR body and branch name. Example: ENG-8061 got two identical "Now available in stable release v0.30.4" comments 1 second apart. Root cause: IssueIDs() extracted from both PR body AND branch name, returning duplicates when both contained the same issue reference. This was exposed by commit e480400 which added stable release comments for already-released issues - before that, duplicates were silently skipped because issue was already in "Released" state. Resolves OPS-460 (cherry picked from commit cfcf45a) Co-authored-by: Piotr <piotr.zaniewski@loft.sh>
Piotr1215
added a commit
that referenced
this pull request
Jan 9, 2026
…) (#3458) Linear sync created duplicate comments on issues when same ID appeared in both PR body and branch name. Example: ENG-8061 got two identical "Now available in stable release v0.30.4" comments 1 second apart. Root cause: IssueIDs() extracted from both PR body AND branch name, returning duplicates when both contained the same issue reference. This was exposed by commit e480400 which added stable release comments for already-released issues - before that, duplicates were silently skipped because issue was already in "Released" state. Resolves OPS-460 (cherry picked from commit cfcf45a) Co-authored-by: Piotr <piotr.zaniewski@loft.sh>
Piotr1215
added a commit
that referenced
this pull request
Jan 9, 2026
…) (#3459) Linear sync created duplicate comments on issues when same ID appeared in both PR body and branch name. Example: ENG-8061 got two identical "Now available in stable release v0.30.4" comments 1 second apart. Root cause: IssueIDs() extracted from both PR body AND branch name, returning duplicates when both contained the same issue reference. This was exposed by commit e480400 which added stable release comments for already-released issues - before that, duplicates were silently skipped because issue was already in "Released" state. Resolves OPS-460 (cherry picked from commit cfcf45a) Co-authored-by: Piotr <piotr.zaniewski@loft.sh>
Piotr1215
added a commit
that referenced
this pull request
Jan 16, 2026
Piotr1215
added a commit
that referenced
this pull request
Jan 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes OPS-460
Note
Prevents duplicate Linear updates by deduplicating issue IDs extracted from PRs before state transitions.
deduplicateIssueIDsand applies it to collectedreleasedIssuesprior to syncingmain_test.govalidate deduplication (duplicates across PRs/body+branch, order preservation, empty/all-dup cases)Written by Cursor Bugbot for commit 03a300b. This will update automatically on new commits. Configure here.