Skip to content

Commit 5755e19

Browse files
hyperpolymathclaude
andcommitted
ci: remove the temporary pull_request trigger from Security Scan
Its purpose is served. Run 29831433656 on commit 4cd3f20 proves the reusable-resolution fix: the workflow parsed for the first time (registry name flipped from `.github/workflows/security-scan.yml` to `Security Scan`), jobs went 0 -> 1, and every step succeeded through `Run scan`. The only failing step is `Send to verisimdb-data`, with ##[error]verisimdb-data dispatch failed with HTTP 401: {"message": "Bad credentials" i.e. the predicted expired `VERISIMDB_PAT`, which is an owner action and is not addressed here. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
1 parent 4cd3f20 commit 5755e19

1 file changed

Lines changed: 7 additions & 4 deletions

File tree

.github/workflows/security-scan.yml

Lines changed: 7 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,10 +5,13 @@ name: Security Scan
55
on:
66
push:
77
branches: [main]
8-
# TEMPORARY (removed before merge): this workflow has no pull_request
9-
# trigger, so a fix to it can never be verified pre-merge. Added so the
10-
# reusable-resolution fix below is proven by an actual run on this PR.
11-
pull_request:
8+
# No `pull_request:` trigger by design -- this scan pushes a report to
9+
# verisimdb-data, which should happen for main, not for every PR. That does
10+
# mean a change to THIS file cannot be verified pre-merge; a temporary
11+
# `pull_request:` trigger was added on this branch to prove the fix below,
12+
# then removed. Verifying run: 29831433656 (commit 4cd3f20) -- the workflow
13+
# loaded, the scan executed, and only the dispatch step failed (HTTP 401,
14+
# expired VERISIMDB_PAT). Re-add the trigger the same way if you touch this.
1215
schedule:
1316
- cron: '0 0 * * 0' # Weekly on Sunday at midnight
1417
workflow_dispatch:

0 commit comments

Comments
 (0)