Detecting and Fixing Duplicate Require Entries

Duplicate Require Entries in go.mod

Duplicate require entries occur when the same module path appears more than once in go.mod. While Go typically handles this gracefully (using the last occurrence), duplicates indicate a problem in the file.

How Duplicates Appear

1. Merge Conflicts When two branches add or update the same dependency, resolving the merge conflict may leave both versions:

require (
    github.com/lib/pq v1.10.7  // from branch A
    github.com/lib/pq v1.10.9  // from branch B
)

2. Manual Editing Adding a dependency manually without checking if it already exists:

require (
    github.com/gin-gonic/gin v1.9.0
    // ... many lines ...
    github.com/gin-gonic/gin v1.9.1  // Oops, already listed above
)

3. Copy-Paste Errors Copying blocks of dependencies from one go.mod to another.

Problems with Duplicates

• Ambiguity: Which version is actually used? (Go uses the last one, but this is confusing)
• Build confusion: Different tools may interpret duplicates differently
• Review difficulty: Hard to determine the actual version from reading the file
• go vet warnings: Some Go tooling will warn about duplicates

Detection

The go.mod formatter detects duplicates by:

1. Scanning all require entries
2. Building a map of module path → version
3. Flagging any path that appears more than once
4. Reporting both versions in the issue list

Automatic Fix

With "Remove duplicates" enabled, the formatter:

1. Processes entries in order
2. Keeps only the last occurrence of each module path
3. This matches Go's behavior (last wins)

Prevention

• Always run go mod tidy after merge conflict resolution
• Use a go.mod formatter in pre-commit hooks
• Enable CI checks for duplicate entries
• Prefer go get over manual edits when updating versions

After Cleanup

After removing duplicates, always verify your build:

go mod tidy
go build ./...
go test ./...