mirror of
https://github.com/sourcegraph/sourcegraph.git
synced 2026-02-06 18:51:59 +00:00
4df176b87e
We cannot use the staticcheck analyzer directly, since it's actually a collection of analyzers. So we have to pull out each "micro" analyzer and create a seperate bazel target with it. Each bazel target actually just uses `staticcheck.go` and embeds the analyzer it SHOULD use when invoked as that target. Ex: ``` bazel build //dev/linters/staticcheck:SA6001 ``` The above target will do the following: * Set `AnalyzerName` to `SA6001` in `staticcheck.go` uses x_def * Set the importpath to `github.com/sourcegraph/sourcegraph/dev/llinters/staticcheck/SA6001`. **This is very important, otherwise there won't be different libraries with different analyzer names, just one library with one analyzer set invoked by different targets**. ## Test plan bazel build //cmd/frontend/... green ci <!-- All pull requests REQUIRE a test plan: https://docs.sourcegraph.com/dev/background-information/testing_principles --> --------- Co-authored-by: Jean-Hadrien Chabran <jh@chabran.fr> |
||
|---|---|---|
| .. | ||
| blobstore | ||
| frontend | ||
| github-proxy | ||
| gitserver | ||
| loadtest | ||
| migrator | ||
| repo-updater | ||
| searcher | ||
| server | ||
| sitemap | ||
| sourcegraph-oss | ||
| symbols | ||
| worker | ||
| README.md | ||
This directory contains Sourcegraph services and binaries.
When a services is added, removed, or when a service's dependencies change, update our architecture diagram.