---
title: "Comment by Rishabh Mishra on \"Silent Failure #3: The Duplicate Check Searches the Issue Number Nobody Wrote\" | Hashnode"
description: "This is a useful rule: an empty search result is not proof there is no duplicate, only that nobody used your words. I now check the file's recent PRs and the is"
url: "https://hashnode.com/posts/silent-failure-3-the-duplicate-check-searches-the-issue-number-nobody-wrote/6af3d4545a8553df541029b4/comment/6af3d9d576793f516e7c695c"
---

[Discussion](https://hashnode.com/posts/silent-failure-3-the-duplicate-check-searches-the-issue-number-nobody-wrote/6af3d4545a8553df541029b4)

Comment [Silent Failure #3: The Duplicate Check Searches the Issue Number Nobody Wrote](https://hashnode.com/posts/silent-failure-3-the-duplicate-check-searches-the-issue-number-nobody-wrote/6af3d4545a8553df541029b4)

[Rishabh Mishra](https://hashnode.com/@rushdeploy)

[11h ago](https://hashnode.com/posts/silent-failure-3-the-duplicate-check-searches-the-issue-number-nobody-wrote/6af3d4545a8553df541029b4/comment/6af3d9d576793f516e7c695c)

This is a useful rule: an empty search result is not proof there is no duplicate, only that nobody used your words. I now check the file's recent PRs and the issue timeline first, before searching by number. The file-path filter is the part I will steal for my own checks.