ci: add CodeQL analysis workflow for java, python and github actions #15243
Conversation
|
This PR does not have an entry in lucene/CHANGES.txt. Consider adding one. If the PR doesn't need a changelog entry, then add the skip-changelog label to it and you will stop receiving this reminder on future updates to the PR. |
|
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
|
This PR does not have an entry in lucene/CHANGES.txt. Consider adding one. If the PR doesn't need a changelog entry, then add the skip-changelog label to it and you will stop receiving this reminder on future updates to the PR. |
We probably only need this for java, but just run it as a matter of fact. CodeQL is working properly, but if we get the tooling correct we may benefit from dependency analysis.
|
This PR does not have an entry in lucene/CHANGES.txt. Consider adding one. If the PR doesn't need a changelog entry, then add the skip-changelog label to it and you will stop receiving this reminder on future updates to the PR. |
|
|
I'm aware the java job takes 5 minutes, I think it is just the nature of a big codebase. If there are resource issues around this, let's just disable the java language (or reduce its queries back down from security extended). |
|
I'll tone down the queries for java language as we now have hundreds of alerts and a lot of them are not security-related (e.g. implicit narrowing of compound assignments), instead just pure noise. Gimme a bit, ill make a PR. |
1 participant
No description provided.