From de236d0d1f8e519a27b15c147a89fb42354250bb Mon Sep 17 00:00:00 2001
From: Steve Yegge <steve.yegge@gmail.com>
Date: Wed, 15 Oct 2025 20:09:24 -0700
Subject: [PATCH] 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.
---
 cmd/bd/import.go | 17 +++++++----------
 1 file changed, 7 insertions(+), 10 deletions(-)

diff --git a/cmd/bd/import.go b/cmd/bd/import.go
index 7926a7ab..835ca9de 100644
--- a/cmd/bd/import.go
+++ b/cmd/bd/import.go
@@ -253,16 +253,13 @@ Behavior:
 		}
 
 		 // Handle duplicates within the same import batch (last one wins)
-		  if idx, ok := seenNew[issue.ID]; ok {
-				if skipUpdate {
-		    skipped++
-		    continue
-				}
-				newIssues[idx] = issue
-			} else {
-				seenNew[issue.ID] = len(newIssues)
-				newIssues = append(newIssues, issue)
-			}
+		 if idx, ok := seenNew[issue.ID]; ok {
+		 // Last one wins regardless of skipUpdate (skipUpdate only applies to existing DB issues)
+		 newIssues[idx] = issue
+		 } else {
+		 seenNew[issue.ID] = len(newIssues)
+		 newIssues = append(newIssues, issue)
+		 }
 		}
 	}