You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+8-1
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,14 @@ Issues that ask questions answered in the FAQ will be closed without elaboration
8
8
9
9
## 2. Search for Duplicates
10
10
11
-
[Search the existing issues](https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93&q=is%3Aissue) before logging a new one.
11
+
[Search the existing issues](https://github.com/Microsoft/TypeScript/search?type=Issues) before logging a new one.
12
+
13
+
Some search tips:
14
+
**Don't* restrict your search to only open issues. An issue with a title similar to yours may have been closed as a duplicate of one with a less-findable title.
15
+
* Check for synonyms. For example, if your bug involves an interface, it likely also occurs with type aliases or classes.
16
+
* Search for the title of the issue you're about to log. This sounds obvious but 80% of the time this is sufficient to find a duplicate when one exists.
17
+
* Read more than the first page of results. Many bugs here use the same words so relevancy sorting is not particularly strong.
18
+
* If you have a crash, search for the first few topmost function names shown in the call stack.
0 commit comments