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: README.md
+17-6Lines changed: 17 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -287,8 +287,11 @@ Excluding a package from any analysis can be achieved by marking the package for
287
287
]
288
288
}
289
289
```
290
+
</li>
291
+
292
+
<li>
293
+
<em>Golang</em> users can add in go.mod a comment with <code>// exhortignore</code> next to the package to be ignored, or to "piggyback" on existing comment ( e.g - <code>// indirect</code>), for example:
290
294
291
-
<em>Golang</em> users can add in go.mod a comment with //exhortignore next to the package to be ignored, or to "piggyback" on existing comment ( e.g - //indirect) , for example:
<b>NOTE</b>: It is important to format <code>exhortignore</code> markers on indirect dependencies as shown above, otherwise the Go tooling (as well as this library) may incorrectly parse dependencies marked as indirect as being direct dependencies instead.
319
+
</li>
320
+
321
+
322
+
<li>
315
323
<em>Python pip</em> users can add in requirements.txt a comment with #exhortignore(or # exhortignore) to the right of the same artifact to be ignored, for example:
324
+
316
325
```properties
317
326
anyio==3.6.2
318
327
asgiref==3.4.1
@@ -343,11 +352,14 @@ Werkzeug==2.0.3
343
352
zipp==3.6.0
344
353
345
354
```
355
+
</li>
346
356
357
+
<li>
347
358
<em>Gradle</em> users can add in build.gradle a comment with //exhortignore next to the package to be ignored:
0 commit comments