ci: Qodana scans for Python, JS/TS and Rust

Three workflows, one per Qodana Cloud project and token
(QODANA_TOKEN_PYTHON, QODANA_TOKEN_TS_JS, QODANA_TOKEN_RUST), each with
the qodana.yaml of its project directory:

- qodana-python.yml: Qodana for Python over scripts/, native mode on the
  runner's Python 3.15 with the hashed requirements installed.
- qodana-js.yml: Qodana for JS over web/, native mode on Node 26 after
  `npm ci --ignore-scripts` and `npm run build:admin`, with the Svelte
  plugin so .svelte files are read.
- qodana-rust.yml: Qodana for Rust (EAP, Docker only) over web/src-tauri/,
  with a stand-in web/dist so generate_context!() expands.

Each runs on pushes to main and pull requests that touch its files, and
by hand. The scan is skipped when its token is not available (forks,
Dependabot), as sonarcloud.yml does; the action is pinned by SHA, the
job's token can read contents and write only checks and PR comments, and
each workflow has its own cache keys so the three do not collide.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
poli0981andClaude Opus 5.5 committed 2026-11-17 08:54:27 +07:00
1 parent d87bf4e2e6
commit 629cb1df75
6 files changed
+389

No files matched your search

+112
View File
@@ -0,0 +1,112 @@
name: Qodana (JS/TS)
# JetBrains Qodana for JS (an Ultimate linter) over web/: the SvelteKit site,
# the admin SPA, the Cloudflare Worker, the shared modules and the build code.
# It reports to its own Qodana Cloud project, whose project token is the
# repository secret QODANA_TOKEN_TS_JS. The pipeline is qodana-python.yml, the
# Tauri shell under web/src-tauri/ is qodana-rust.yml; what each scan reads and
# ignores is the qodana.yaml in its project directory.
#
# Native mode (web/qodana.yaml, `withinDocker: false`): the analysis runs on
# this runner, with the Node every other workflow uses and node_modules
# installed exactly as web-ci.yml installs it. The Qodana image brings an
# older Node, and would have to install the packages itself.
on:
push:
branches: [main]
paths:
- 'web/**'
- '!web/src-tauri/**'
- '.github/workflows/qodana-js.yml'
pull_request:
types: [opened, synchronize, reopened]
paths:
- 'web/**'
- '!web/src-tauri/**'
- '.github/workflows/qodana-js.yml'
workflow_dispatch:
permissions: {}
concurrency:
group: qodana-js-${{ github.ref }}
cancel-in-progress: ${{ github.event_name == 'pull_request' }}
jobs:
# Pull requests from forks and from Dependabot get no repository secrets,
# and an Ultimate linter will not run without the token, so the scan is
# skipped rather than failing every such pull request (as sonarcloud.yml).
token:
runs-on: ubuntu-latest
timeout-minutes: 5
outputs:
present: ${{ steps.check.outputs.present }}
steps:
- name: Check for the token
id: check
env:
HAS_TOKEN: ${{ secrets.QODANA_TOKEN_TS_JS != '' }}
run: |
echo "present=$HAS_TOKEN" >> "$GITHUB_OUTPUT"
if [ "$HAS_TOKEN" != "true" ]; then
echo "::notice::QODANA_TOKEN_TS_JS is not available to this run; skipping the Qodana scan."
fi
scan:
needs: token
if: needs.token.outputs.present == 'true'
runs-on: ubuntu-latest
timeout-minutes: 40
permissions:
contents: read
checks: write # annotations on the commit
pull-requests: write # the summary comment on a pull request
steps:
# The pull request's own head commit, not the merge GitHub makes, so the
# report and its annotations name commits that exist; full history, as
# Qodana Cloud's setup snippet has it.
- uses: actions/checkout@v6
with:
ref: ${{ github.event.pull_request.head.sha }}
fetch-depth: 0
persist-credentials: false
- uses: actions/setup-node@v7
with:
node-version: '26'
cache: 'npm'
cache-dependency-path: web/package-lock.json
# --ignore-scripts, as everywhere this repo runs `npm ci` (web-ci.yml
# says why).
- name: Install web/
working-directory: web
run: npm ci --ignore-scripts
# `svelte-kit sync` writes the tsconfig web/tsconfig.json extends and the
# route types, and the admin build writes worker/generated/, which
# worker/index.ts imports. Without them the analysis reads the app
# untyped and the Worker with an unresolved import (sonarcloud.yml does
# the same before its scan).
- name: Generate SvelteKit's types and the admin bundle
working-directory: web
run: npm run build:admin
# web/ is the project. The cache keys name the linter: the three Qodana
# workflows run on the same commits, and the action's default keys would
# collide. pr-mode false: a pull request is analysed whole, as Qodana
# Cloud's setup suggests, not only the files it changes.
- name: Qodana scan
uses: JetBrains/qodana-action@3e8d76ff0e0241618abd808682f426afe84bab3f # v2026.2.2
with:
args: --project-dir web
pr-mode: false
upload-result: true
artifact-name: qodana-js
primary-cache-key: qodana-2026.2-js-${{ github.ref }}-${{ github.sha }}
additional-cache-key: qodana-2026.2-js-${{ github.ref }}
cache-default-branch-only: true
env:
QODANA_TOKEN: ${{ secrets.QODANA_TOKEN_TS_JS }}
QODANA_ENDPOINT: 'https://qodana.cloud'
+111
View File
@@ -0,0 +1,111 @@
name: Qodana (Python)
# JetBrains Qodana for Python (an Ultimate linter) over scripts/, the data
# pipeline and its tests. It reports to its own Qodana Cloud project, whose
# project token is the repository secret QODANA_TOKEN_PYTHON. The site and the
# Worker are qodana-js.yml, the Tauri shell is qodana-rust.yml; what each scan
# reads and ignores is the qodana.yaml in its project directory.
#
# Native mode (scripts/qodana.yaml, `withinDocker: false`): the analysis runs
# on this runner, so it sees the Python the pipeline runs on and the pinned
# packages, installed exactly as python-tests.yml installs them. The Qodana
# image would bring its own, older interpreter and none of the packages.
on:
push:
branches: [main]
# The pipeline's code, not the queues and logs the data jobs commit
# beside it (scripts/*.jsonl, scripts/*.log).
paths:
- 'scripts/**/*.py'
- 'scripts/qodana.yaml'
- 'requirements.txt'
- 'requirements-test.txt'
- '.github/workflows/qodana-python.yml'
pull_request:
types: [opened, synchronize, reopened]
paths:
- 'scripts/**/*.py'
- 'scripts/qodana.yaml'
- 'requirements.txt'
- 'requirements-test.txt'
- '.github/workflows/qodana-python.yml'
workflow_dispatch:
permissions: {}
concurrency:
group: qodana-python-${{ github.ref }}
cancel-in-progress: ${{ github.event_name == 'pull_request' }}
jobs:
# Pull requests from forks and from Dependabot get no repository secrets,
# and an Ultimate linter will not run without the token, so the scan is
# skipped rather than failing every such pull request (as sonarcloud.yml).
token:
runs-on: ubuntu-latest
timeout-minutes: 5
outputs:
present: ${{ steps.check.outputs.present }}
steps:
- name: Check for the token
id: check
env:
HAS_TOKEN: ${{ secrets.QODANA_TOKEN_PYTHON != '' }}
run: |
echo "present=$HAS_TOKEN" >> "$GITHUB_OUTPUT"
if [ "$HAS_TOKEN" != "true" ]; then
echo "::notice::QODANA_TOKEN_PYTHON is not available to this run; skipping the Qodana scan."
fi
scan:
needs: token
if: needs.token.outputs.present == 'true'
runs-on: ubuntu-latest
timeout-minutes: 30
permissions:
contents: read
checks: write # annotations on the commit
pull-requests: write # the summary comment on a pull request
steps:
# The pull request's own head commit, not the merge GitHub makes, so the
# report and its annotations name commits that exist; full history, as
# Qodana Cloud's setup snippet has it.
- uses: actions/checkout@v6
with:
ref: ${{ github.event.pull_request.head.sha }}
fetch-depth: 0
persist-credentials: false
- uses: actions/setup-python@v6
with:
python-version: '3.15'
# Hash mode is all-or-nothing per pip call, hence two (python-tests.yml).
# The tests are analysed too, so pytest has to resolve.
- name: Install the pipeline and the test tools
run: |
pip install --quiet --require-hashes --only-binary :all: -r requirements.txt
pip install --quiet --require-hashes --only-binary :all: -r requirements-test.txt
# scripts/ is the project, not the repository root: every script and the
# tests put scripts/ on sys.path and import `core`, which resolves only
# when scripts/ is the content root. The repository root is still found
# (git), so the report's paths and links are the repository's.
# The cache keys name the linter: the three Qodana workflows run on the
# same commits, and the action's default keys would collide.
# pr-mode false: a pull request is analysed whole, as Qodana Cloud's
# setup suggests, not only the files it changes.
- name: Qodana scan
uses: JetBrains/qodana-action@3e8d76ff0e0241618abd808682f426afe84bab3f # v2026.2.2
with:
args: --project-dir scripts
pr-mode: false
upload-result: true
artifact-name: qodana-python
primary-cache-key: qodana-2026.2-python-${{ github.ref }}-${{ github.sha }}
additional-cache-key: qodana-2026.2-python-${{ github.ref }}
cache-default-branch-only: true
env:
QODANA_TOKEN: ${{ secrets.QODANA_TOKEN_PYTHON }}
QODANA_ENDPOINT: 'https://qodana.cloud'
+100
View File
@@ -0,0 +1,100 @@
name: Qodana (Rust)
# JetBrains Qodana for Rust (an Ultimate linter, Early Access in 2026.2) over
# web/src-tauri/, the Tauri 2 desktop and Android shell. It reports to its own
# Qodana Cloud project, whose project token is the repository secret
# QODANA_TOKEN_RUST. The pipeline is qodana-python.yml, the rest of web/ is
# qodana-js.yml; what each scan reads and ignores is the qodana.yaml in its
# project directory.
#
# Docker mode: Qodana for Rust has no native mode. The CLI mounts the whole
# repository into the container (the project directory is inside it), and the
# image brings its own Rust toolchain.
on:
push:
branches: [main]
paths:
- 'web/src-tauri/**'
- '!web/src-tauri/gen/**'
- '.github/workflows/qodana-rust.yml'
pull_request:
types: [opened, synchronize, reopened]
paths:
- 'web/src-tauri/**'
- '!web/src-tauri/gen/**'
- '.github/workflows/qodana-rust.yml'
workflow_dispatch:
permissions: {}
concurrency:
group: qodana-rust-${{ github.ref }}
cancel-in-progress: ${{ github.event_name == 'pull_request' }}
jobs:
# Pull requests from forks and from Dependabot get no repository secrets,
# and an Ultimate linter will not run without the token, so the scan is
# skipped rather than failing every such pull request (as sonarcloud.yml).
token:
runs-on: ubuntu-latest
timeout-minutes: 5
outputs:
present: ${{ steps.check.outputs.present }}
steps:
- name: Check for the token
id: check
env:
HAS_TOKEN: ${{ secrets.QODANA_TOKEN_RUST != '' }}
run: |
echo "present=$HAS_TOKEN" >> "$GITHUB_OUTPUT"
if [ "$HAS_TOKEN" != "true" ]; then
echo "::notice::QODANA_TOKEN_RUST is not available to this run; skipping the Qodana scan."
fi
scan:
needs: token
if: needs.token.outputs.present == 'true'
runs-on: ubuntu-latest
timeout-minutes: 45
permissions:
contents: read
checks: write # annotations on the commit
pull-requests: write # the summary comment on a pull request
steps:
# The pull request's own head commit, not the merge GitHub makes, so the
# report and its annotations name commits that exist; full history, as
# Qodana Cloud's setup snippet has it.
- uses: actions/checkout@v6
with:
ref: ${{ github.event.pull_request.head.sha }}
fetch-depth: 0
persist-credentials: false
# tauri::generate_context!() embeds frontendDist (../dist) when it
# expands, and fails when the directory is missing. The analysis needs
# the macro to expand, not the site, so a stand-in page is enough; the
# real build is the release workflows'.
- name: Stand in for the frontend build
run: |
mkdir -p web/dist
printf '<!doctype html>\n<title>F2P Tracker</title>\n' > web/dist/index.html
# web/src-tauri/ is the project: its Cargo.toml is the crate. The cache
# keys name the linter: the three Qodana workflows run on the same
# commits, and the action's default keys would collide. pr-mode false: a
# pull request is analysed whole, as Qodana Cloud's setup suggests, not
# only the files it changes.
- name: Qodana scan
uses: JetBrains/qodana-action@3e8d76ff0e0241618abd808682f426afe84bab3f # v2026.2.2
with:
args: --project-dir web/src-tauri
pr-mode: false
upload-result: true
artifact-name: qodana-rust
primary-cache-key: qodana-2026.2-rust-${{ github.ref }}-${{ github.sha }}
additional-cache-key: qodana-2026.2-rust-${{ github.ref }}
cache-default-branch-only: true
env:
QODANA_TOKEN: ${{ secrets.QODANA_TOKEN_RUST }}
QODANA_ENDPOINT: 'https://qodana.cloud'
+22
View File
@@ -0,0 +1,22 @@
# Qodana for Python over the data pipeline (.github/workflows/qodana-python.yml,
# Qodana Cloud project token QODANA_TOKEN_PYTHON).
#
# This directory is the project, not the repository root: every script and
# the tests put scripts/ on sys.path and import `core`, which resolves only
# when scripts/ is the content root.
version: "1.0"
linter: qodana-python
# Native mode: the runner's Python 3.15 with requirements.txt and
# requirements-test.txt installed, as the pipeline itself runs.
withinDocker: false
profile:
name: qodana.recommended
inspections:
# Data, not code: the queues and the log the data jobs commit here, and
# the byte-exact blocklist golden file the tests compare against.
- group: ALL
ignore:
- "removed_games.jsonl"
- "temp_info.jsonl"
- "dead_games.log"
- "tests/fixtures"
+30
View File
@@ -0,0 +1,30 @@
# Qodana for JS over web/ (.github/workflows/qodana-js.yml, Qodana Cloud
# project token QODANA_TOKEN_TS_JS): the site, the admin SPA, the Worker, the
# shared modules and the build code. src-tauri/ is Rust, and has its own scan
# (qodana-rust.yml, src-tauri/qodana.yaml).
version: "1.0"
linter: qodana-js
# Native mode: the runner's Node 26 with node_modules installed by
# `npm ci --ignore-scripts`, and the files `npm run build:admin` generates
# (the workflow runs both first).
withinDocker: false
# The components are .svelte files, which the linter reads only with
# JetBrains' Svelte plugin; it is not bundled with Qodana for JS.
plugins:
- id: dev.blachut.svelte.lang
profile:
name: qodana.recommended
inspections:
- group: ALL
ignore:
# The Tauri shell: Rust, and the generated Android project.
- "src-tauri"
# Generated: by the build (dist, .admin-build), by `svelte-kit sync`
# (.svelte-kit), by the admin build for the Worker (worker/generated),
# by the coverage run (coverage). The types in them still resolve;
# they are only not reported on.
- "dist"
- ".admin-build"
- ".svelte-kit"
- "worker/generated"
- "coverage"
+14
View File
@@ -0,0 +1,14 @@
# Qodana for Rust over the Tauri 2 shell (.github/workflows/qodana-rust.yml,
# Qodana Cloud project token QODANA_TOKEN_RUST). Early Access in 2026.2, and
# Docker only: the image brings its own Rust toolchain.
version: "1.0"
linter: qodana-rust
profile:
name: qodana.recommended
inspections:
- group: ALL
ignore:
# Generated by `tauri android init`, and Kotlin/Gradle, not Rust.
- "gen"
# Cargo's build output.
- "target"