Files
pipdock/.github/workflows/notify-ci-failure.yml
T
poli0981andClaude Opus 5.5 4a617722d6 ci(sonar): CI-based SonarQube Cloud analysis, with Rust and TypeScript coverage (#85)
Automatic analysis could not build, so it never analysed the Rust two
thirds of the code and imported no coverage; it also sent no project
version, leaving the previous-version new-code period anchored to the
first analysis. sonar.yml runs on Windows, produces cargo-llvm-cov and
vitest LCOV plus clippy's JSON, and scans with sonarqube-scan-action
v8.3.0 (pinned), passing the version from package.json. The token
reaches the scan step alone; the job is skipped without one (Dependabot,
forks) and refuses a dispatch off main, which this plan cannot analyse.

Unblocks the required audits, red on main since 2026-10-21:
rustls-webpki 0.103.16, webpki-root-certs 1.0.11, clipboard-win 5.4.3,
zod 4.6.7. Dependabot groups vitest with @vitest/*.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-25 06:38:10 +07:00

31 lines
913 B
YAML

# Caller into the ops repo's Discord CI-failure notifier.
#
# **Listed by name.** `workflows: ['*']`, which the ops repo's own example suggests, is not a
# wildcard to `workflow_run`: it matched nothing, so `main` stayed red from 2026-09-23 with every
# failure unreported — the only runs this ever saw were Dependabot's. Adding a workflow means
# adding its `name:` here, exactly.
#
# CodeQL and Release are deliberately absent: the reusable skips workflows with dedicated
# notifiers by name ('odeQL', 'elease', …), so listing them would only create skipped runs.
name: Notify CI Failure
on:
workflow_run:
workflows:
- CI / Rust
- CI / Node
- CI / Integration
- Security scan
- SonarCloud
types: [completed]
permissions:
contents: read
actions: read
jobs:
notify:
uses: poli0981/.github/.github/workflows/notify-ci-failure.yml@main
secrets: inherit