dedupe-issue-local

Duplicate detection for issue triage can be customized by applying repo-specific normalization rules and override categories to refine titles, prefixes, and contextual signals without altering the underlying similarity algorithm.

Issue normalization is the process of standardizing issue titles by stripping prefixes like Bug: or Feature: to improve cross-repo duplicate detection accuracy for issues and reports.

Yes, you can use configurable normalization steps and overridable categories within the dedupe-issue workflow to tailor duplicate detection while keeping the core dedupe algorithm intact.

Repo-specific prefix stripping during issue triage is handled by applying configurable normalization rules that remove project-specific prefixes such as Warp: before running the duplicate detection algorithm.

Yes, the dedupe-issue workflow supports project-tailored refinements to contextual signals by enabling overridable categories and normalization rules specific to the warp-external repository.

Repo-specific normalization rules are needed for duplicate issue detection because core dedupe rules require project-tailored refinements to accurately match issues with varying prefixes and contextual signals.