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
We are trying to set up incremental scanning in our CI pipeline using [Tool Name], but we couldn't find any relevant flags or options for this. Could anyone provide guidance on how to achieve this, or let us know if such a feature is supported。
The text was updated successfully, but these errors were encountered:
Due to the sophistication of the analyses that NilAway does, NilAway caches its findings about a particular package via the Fact Mechanism from the go/analysis framework. Therefore, it is highly recommended to leverage a driver that supports modular analysis (i.e., bazel/nogo or golangci-lint, but not the standalone checker since it stores all facts in memory) for better performance on large projects. The standalone checker is provided more for evaluation purposes since it is easy to get started.
It only caches its findings in memory, so in the next run everything has to be re-analyzed again.
We recommend using a proper analyzer driver, like golangci-lint (see instructions), or if you're using bazel as your build system - bazel/nogo for proper caching of the facts.
We are trying to set up incremental scanning in our CI pipeline using [Tool Name], but we couldn't find any relevant flags or options for this. Could anyone provide guidance on how to achieve this, or let us know if such a feature is supported。
The text was updated successfully, but these errors were encountered: