Fix skip-existing logic for batch import duplicates

The skipUpdate flag should only apply to existing DB issues, not to
duplicates within the import batch. Batch duplicates always use
last-one-wins semantics.
This commit is contained in:
Steve Yegge
2025-10-15 20:09:24 -07:00
parent 3eb4f4d040
commit de236d0d1f

View File

@@ -254,10 +254,7 @@ Behavior:
// Handle duplicates within the same import batch (last one wins)
if idx, ok := seenNew[issue.ID]; ok {
if skipUpdate {
skipped++
continue
}
// Last one wins regardless of skipUpdate (skipUpdate only applies to existing DB issues)
newIssues[idx] = issue
} else {
seenNew[issue.ID] = len(newIssues)