-
Notifications
You must be signed in to change notification settings - Fork 14.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add CodeQL security scanning on pull requests. #44404
Add CodeQL security scanning on pull requests. #44404
Conversation
Apparently we only run codeql on main, but we could run it on PRs as well. That's a good idea to test how it can look like.
This seems to work well. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM +1
Should we just mark 2-10* specifically?
We have the same pattern elsewhere - and we are going to have 2.11 in the future, so better to keep it this way I think. |
And in the future we will have 3_0, 3_1 etc. .... |
Apparently we only run codeql on main, but we could run it on PRs as well. That's a good idea to test how it can look like.
Apparently we only run codeql on main, but we could run it on PRs as well. That's a good idea to test how it can look like.
Apparently we only run codeql on main, but we could run it on PRs as well. That's a good idea to test how it can look like.
Apparently we only run codeql on main, but we could run it on PRs as well. That's a good idea to test how it can look like.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rst
or{issue_number}.significant.rst
, in newsfragments.