LGTM - a code analysis platform for identifying vulnerabilities and preventing them from reaching production. #99
Replies: 7 comments
-
BTW your repository needs a |
Beta Was this translation helpful? Give feedback.
-
I just learned that the environment running the LGTM analysis does not support Docker (when the |
Beta Was this translation helpful? Give feedback.
-
Will it just run on MR ? |
Beta Was this translation helpful? Give feedback.
-
Yes, when a new PR is opened against your repo it should be there as an additional check |
Beta Was this translation helpful? Give feedback.
-
LGTM will be shutdown in December 2022: https://github.blog/2022-08-15-the-next-step-for-lgtm-com-github-code-scanning/, the recommendation is to use GitHub Code Scanning instead |
Beta Was this translation helpful? Give feedback.
-
@gastaldi Just wanted to make sure I understood the link correctly - no immediate action is needed on our part, correct? GitHub will submit PRs in October to each repo for the migration from LGTM to GitHub Code Scanning, and once we merge that PR in, we would just go ahead and disable LGTM? |
Beta Was this translation helpful? Give feedback.
-
@shumonsharif yes, that's correct. |
Beta Was this translation helpful? Give feedback.
-
LGTM is a code analysis platform for finding zero-days and preventing critical vulnerabilities. We have enabled the application in the Quarkiverse organization to build PRs but only for a few repositories for the time being.
If you're an extension maintainer and wish to enable LGTM in your Quarkiverse repository, send a PR in the quarkiverse-devops repository
NOTE: The branch must be created in the same repository, it won't work in a separate fork (@quarkiverse/quarkiverse-members should be able to create new branches there)
Here is how the PR should look like: quarkiverse/quarkiverse-devops@c9382dd
Beta Was this translation helpful? Give feedback.
All reactions