-
Notifications
You must be signed in to change notification settings - Fork 0
48 lines (41 loc) · 1.75 KB
/
Copy pathcodeql.yml
File metadata and controls
48 lines (41 loc) · 1.75 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
name: CodeQL
# Static analysis on every pull request, so a finding arrives while the change is still being
# read rather than in a weekly digest nobody opens. `security-and-quality` rather than the
# default suite: this is a small codebase in the execution path of consequential actions, and
# the extra queries cost a few minutes that a project this size can afford.
#
# Findings land in the repository's code-scanning tab. Nothing here gates a merge -- the
# required checks stay `check (3.11)` through `check (3.14)` and `package` -- because a static
# analyser's first run on an unfamiliar codebase is a reading list, not a verdict.
on:
pull_request:
push:
branches: [main]
schedule:
- cron: "41 5 * * 1"
permissions:
contents: read
jobs:
analyze:
name: Analyze Python
runs-on: ubuntu-latest
timeout-minutes: 20
permissions:
security-events: write # to upload the findings to code scanning
contents: read
steps:
- uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
with:
persist-credentials: false
- uses: github/codeql-action/init@cdf488f595d80d6e07e03d4674febd5ab45fa938 # v4.37.9
with:
languages: python
# The core is stdlib plus pyyaml and click, and every extra is imported lazily, so
# there is nothing to build and nothing to install for the analyser to see the code.
build-mode: none
queries: security-and-quality
# Which of that suite's queries this repository acts on, and why two of them are not.
config-file: ./.github/codeql/codeql-config.yml
- uses: github/codeql-action/analyze@cdf488f595d80d6e07e03d4674febd5ab45fa938 # v4.37.9
with:
category: "/language:python"