1
0
mirror of https://github.com/systemd/systemd.git synced 2024-12-22 17:35:35 +03:00

doc: drop remaining references to LGTM.com

This commit is contained in:
Yu Watanabe 2022-09-23 07:54:12 +09:00
parent a79f5097e7
commit 0b0cdb1652
3 changed files with 8 additions and 8 deletions

View File

@ -198,6 +198,6 @@ can be found under various directories such as `factory/`, `modprobe.d/`, `netwo
## Utilities for Developers ## Utilities for Developers
`tools/`, `coccinelle/`, `.github/`, `.semaphore/`, `.lgtm/`, `.mkosi/` host various `tools/`, `coccinelle/`, `.github/`, `.semaphore/`, `.mkosi/` host various
utilities and scripts that are used by maintainers and developers. They are not utilities and scripts that are used by maintainers and developers. They are not
shipped or installed. shipped or installed.

View File

@ -69,9 +69,9 @@ available functionality:
13. When building systemd from a git checkout the build scripts will 13. When building systemd from a git checkout the build scripts will
automatically enable a git commit hook that ensures whitespace cleanliness. automatically enable a git commit hook that ensures whitespace cleanliness.
14. [LGTM](https://lgtm.com/) analyzes every commit pushed to `main`. The list 14. [CodeQL](https://codeql.github.com/) analyzes each PR and every commit
of active alerts can be found pushed to `main`. The list of active alerts can be found
[here](https://lgtm.com/projects/g/systemd/systemd/alerts/?mode=list). [here](https://github.com/systemd/systemd/security/code-scanning).
15. Each PR is automatically tested with [Address Sanitizer](https://clang.llvm.org/docs/AddressSanitizer.html) 15. Each PR is automatically tested with [Address Sanitizer](https://clang.llvm.org/docs/AddressSanitizer.html)
and [Undefined Behavior Sanitizer](https://clang.llvm.org/docs/UndefinedBehaviorSanitizer.html). and [Undefined Behavior Sanitizer](https://clang.llvm.org/docs/UndefinedBehaviorSanitizer.html).

View File

@ -211,10 +211,10 @@ where --test-name= is the name of the test you want to run/debug. The
--shell-fail option will pause the execution in case the test fails and shows --shell-fail option will pause the execution in case the test fails and shows
you the information how to connect to the testbed for further debugging. you the information how to connect to the testbed for further debugging.
Manually running LGTM/CodeQL analysis Manually running CodeQL analysis
===================================== =====================================
This is mostly useful for debugging various CodeQL/LGTM quirks. This is mostly useful for debugging various CodeQL quirks.
Download the CodeQL Bundle from https://github.com/github/codeql-action/releases Download the CodeQL Bundle from https://github.com/github/codeql-action/releases
and unpack it somewhere. From now the 'tutorial' assumes you have the `codeql` and unpack it somewhere. From now the 'tutorial' assumes you have the `codeql`
@ -238,9 +238,9 @@ This can occur if the specified build commands failed to compile or process any
- For other languages, the --command must specify a "clean" build which compiles - For other languages, the --command must specify a "clean" build which compiles
all the source code files without reusing existing build artefacts. all the source code files without reusing existing build artefacts.
If you want to run all queries systemd uses in LGTM/CodeQL, run: If you want to run all queries systemd uses in CodeQL, run:
$ codeql database analyze codeqldb/ --format csv --output results.csv .github/codeql-custom.qls .lgtm/cpp-queries/*.ql -vvv $ codeql database analyze codeqldb/ --format csv --output results.csv .github/codeql-custom.qls .github/codeql-queries/*.ql -vvv
Note: this will take a while. Note: this will take a while.