[duplicate-code] Duplicate Code Analysis Report

[github-actions]

Summary

Analysis of the Go codebase identified 3 significant duplication patterns across internal/server, internal/proxy, and internal/difc packages. Overall severity is Medium — the patterns are actionable and refactorable without major risk.

Detected Patterns

This analysis found 3 significant duplication patterns:

1. get_collaborator_permission GitHub REST Call Logic – Severity: High – See sub-issue [duplicate-code] Duplicate Code Pattern: get_collaborator_permission GitHub REST Call Logic #4459
2. DIFC Component Initialization Sequence – Severity: Medium – See sub-issue [duplicate-code] Duplicate Code Pattern: DIFC Component Initialization Sequence #4460
3. GitHub API Request Headers Setup – Severity: Low – See sub-issue [duplicate-code] Duplicate Code Pattern: GitHub API Request Header Setup #4461

Overall Impact

• Total Duplicated Lines: ~70 lines
• Affected Files: 2–3 files per pattern (internal/server/unified.go, internal/proxy/proxy.go)
• Maintainability Risk: Medium — duplicate GitHub API call logic could diverge (different auth handling, error messages), and DIFC init blocks may be updated inconsistently
• Refactoring Priority: Pattern 1 (collaborator permission) is the highest priority; it has a natural extraction point in the existing internal/mcp package

Next Steps

1. Review individual pattern sub-issues for detailed analysis
2. Prioritize refactoring Pattern 1 (collaborator permission REST call) by extracting to internal/mcp or a new internal/github HTTP utility
3. Consider a difc.NewDIFCComponents(mode string) constructor to unify Pattern 2

Analysis Metadata

• Analyzed Files: Non-test .go files in internal/ (22,075 lines across ~60 files)
• Detection Method: Semantic pattern search and code review
• Commit: 9bc144cdc54a235caf3f685a25a4392106c987ef
• Analysis Date: 2026-04-24