Add CodeQL workflow for GitHub code scanning

[lgtm-com]

Hi vyperlang/vyper!

This is a one-off automatically generated pull request from LGTM.com 🤖. You might have heard that we’ve integrated LGTM’s underlying CodeQL analysis engine natively into GitHub. The result is GitHub code scanning!

With LGTM fully integrated into code scanning, we are focused on improving CodeQL within the native GitHub code scanning experience. In order to take advantage of current and future improvements to our analysis capabilities, we suggest you enable code scanning on your repository. Please take a look at our blog post for more information.

This pull request enables code scanning by adding an auto-generated codeql.yml workflow file for GitHub Actions to your repository — take a look! We tested it before opening this pull request, so all should be working ✔️. In fact, you might already have seen some alerts appear on this pull request!

Where needed and if possible, we’ve adjusted the configuration to the needs of your particular repository. But of course, you should feel free to tweak it further! Check this page for detailed documentation.

Questions? Check out the FAQ below!

FAQ

Click here to expand the FAQ section

How often will the code scanning analysis run?

By default, code scanning will trigger a scan with the CodeQL engine on the following events:

• On every pull request — to flag up potential security problems for you to investigate before merging a PR.
• On every push to your default branch and other protected branches — this keeps the analysis results on your repository’s Security tab up to date.
• Once a week at a fixed time — to make sure you benefit from the latest updated security analysis even when no code was committed or PRs were opened.

What will this cost?

Nothing! The CodeQL engine will run inside GitHub Actions, making use of your unlimited free compute minutes for public repositories.

What types of problems does CodeQL find?

The CodeQL engine that powers GitHub code scanning is the exact same engine that powers LGTM.com. The exact set of rules has been tweaked slightly, but you should see almost exactly the same types of alerts as you were used to on LGTM.com: we’ve enabled the security-and-quality query suite for you.

How do I upgrade my CodeQL engine?

No need! New versions of the CodeQL analysis are constantly deployed on github.com; your repository will automatically benefit from the most recently released version.

The analysis doesn’t seem to be working

If you get an error in GitHub Actions that indicates that CodeQL wasn’t able to analyze your code, please follow the instructions here to debug the analysis.

How do I disable LGTM.com?

If you have LGTM’s automatic pull request analysis enabled, then you can follow these steps to disable the LGTM pull request analysis. You don’t actually need to remove your repository from LGTM.com; it will automatically be removed in the next few months as part of the deprecation of LGTM.com (more info here).

Which source code hosting platforms does code scanning support?

GitHub code scanning is deeply integrated within GitHub itself. If you’d like to scan source code that is hosted elsewhere, we suggest that you create a mirror of that code on GitHub.

How do I know this PR is legitimate?

This PR is filed by the official LGTM.com GitHub App, in line with the deprecation timeline that was announced on the official GitHub Blog. The proposed GitHub Action workflow uses the official open source GitHub CodeQL Action. If you have any other questions or concerns, please join the discussion here in the official GitHub community!

I have another question / how do I get in touch?

Please join the discussion here to ask further questions and send us suggestions!

[codecov-commenter]

Codecov Report

Merging #3147 (2d281f5) into master (046ea16) will decrease coverage by 0.04%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master    #3147      +/-   ##
==========================================
- Coverage   88.48%   88.43%   -0.05%     
==========================================
  Files          85       88       +3     
  Lines       10756    11047     +291     
  Branches     2286     2338      +52     
==========================================
+ Hits         9517     9769     +252     
- Misses        789      823      +34     
- Partials      450      455       +5     

Impacted Files	Coverage Δ
vyper/ast/validation.py	77.55% <0.00%> (-1.62%)	⬇️
vyper/compiler/phases.py	91.07% <0.00%> (ø)
vyper/codegen/global_context.py	74.31% <0.00%> (ø)
vyper/compiler/__init__.py	88.09% <0.00%> (ø)
vyper/__init__.py	58.82% <0.00%> (ø)
vyper/utils.py	83.80% <0.00%> (ø)
vyper/codegen/ir_node.py	91.72% <0.00%> (+0.02%)	⬆️
vyper/ast/signatures/function_signature.py	89.55% <0.00%> (+0.07%)	⬆️
vyper/ast/nodes.py	93.93% <0.00%> (+0.09%)	⬆️
vyper/semantics/analysis/local.py	91.21% <0.00%> (+0.10%)	⬆️
... and 7 more

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[charles-cooper]

looks ok to me. @fubuloubu what do you think? i'm not sure we need that cron job there.

[fubuloubu]

Okay to merge if warnings and info do not carry over to every PR