[Bug]: PR getting tagged as a duplicate for matching the related issue

[Kavirubc]

Bug Description

When the comments are added to the PR, the issue related to that same PR is getting noted as a duplicate. This need to be fixed

Steps to Reproduce

Create an issue
Create a PR
You can see the issue in the comment

Expected Behavior

Actual Behavior

Configuration

Logs

Simili Triage Report
Note

Quality Score: 9.5/10 (Excellent)
The issue could be improved. See suggestions below.

Classification
Category	Value
Labels	 
Quality Improvements
Similar Threads
Warning

Possible Duplicate (Confidence: 95%)
This issue might be a duplicate of #71.
Reason: Issue #71, titled 'ci: add E2E integration test pipeline', is virtually identical in its request to the current issue, titled '[0.2.0][CI] Add E2E integration test pipeline'. Both describe the exact same feature request: to implement an end-to-end integration test pipeline for the Simili Bot. The detailed solution provided in the current issue would fully resolve the request in Issue #71, indicating the same root cause (lack of automated E2E testing) and the same expected outcome (a functional E2E test pipeline).

Simili Version

Other (please specify in description)

Environment

GitHub Actions

Checklist

• I have searched existing issues to ensure this bug hasn't been reported
• I have removed any sensitive information from logs and config

[gh-simili-bot]

Simili Triage Report

Tip

Quality Score: 2.5/10 (Poor)
The issue could be improved. See suggestions below.

Classification

Category	Value
Labels

Quality Improvements

• Missing Expected Behavior
• Missing Actual Behavior
• Reproduction steps are too vague
• Missing configuration details
• Missing relevant logs for the described bug
• Bug description is vague
• Irrelevant log information included
• Describe the Expected Behavior clearly
• Describe the Actual Behavior clearly
• Provide specific, detailed steps to reproduce the bug (e.g., exact issue/PR content, specific comment that triggers the bug)
• Include relevant configuration details (e.g., bot version, GitHub environment)
• Provide actual logs or screenshots demonstrating the issue (e.g., the bot's comment tagging the PR as duplicate)
• Clarify the bug description to specify what system is doing the tagging and under what exact conditions
• Remove the irrelevant 'Simili Triage Report' as it pertains to a different issue evaluation

Similar Threads

Similarity	Thread	Status
85%	#59 [Bug]: Closed Issues and PRs are shown as Open ...	Open
81%	#72 [0.2.0][CI] Add E2E integration test pipeline	Open
81%	#54 Enhancement: Two-phase duplicate detection with...	Open

---

_{Generated by Simili Bot}

[gh-simili-bot]

Simili Triage Report

Tip

Quality Score: 2.0/10 (Poor)
The issue could be improved. See suggestions below.

Classification

Category	Value
Labels

Quality Improvements

• Missing Expected Behavior
• Missing Actual Behavior
• Vague reproduction steps
• Missing relevant configuration details
• Missing relevant logs
• Bug description lacks specific details
• Irrelevant content in logs section
• Clearly describe the expected behavior
• Clearly describe the actual behavior, including how it's 'noted as a duplicate'
• Provide detailed, step-by-step instructions to reproduce the bug, including specific actions and inputs
• Specify the exact comments or actions that trigger the issue
• Include relevant configuration details (e.g., version of the system, specific settings)
• Provide actual error messages or relevant system logs that show the 'duplicate' tagging
• Remove irrelevant content from the logs section

Similar Threads

Similarity	Thread	Status
85%	#59 [Bug]: Closed Issues and PRs are shown as Open ...	Open
81%	#72 [0.2.0][CI] Add E2E integration test pipeline	Open
81%	#54 Enhancement: Two-phase duplicate detection with...	Open

---

_{Generated by Simili Bot}