Repository navigation
ci: run the scan and link check in verify - #205
Conversation
Replace the Scan and Links caller workflows with the shared putdotio/.github scan and links actions as the last steps of the verify job. CI now also runs on manual dispatch, the full-history scan; the release job stays push-only.
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
There was a problem hiding this comment.
Copilot review overview
🔵 Needs a closer look
It restructures the security-scanning and release-gating pipeline (dropping PR-time Actionlint/Zizmor and the weekly scheduled scan, and coupling link/scan results to release gating), which warrants human review of the security posture tradeoffs.
Review effort: Balanced
Findings: 1
Open (1)
What changed in this PR
This PR consolidates two separate CI workflows into the main ci.yml pipeline. The secret/workflow scan and the offline Markdown link check previously ran as their own scan.yml and links.yml workflows; they are now appended as steps at the end of the Verify SDK job using the shared putdotio/.github composite actions (actions/links and actions/scan, pinned to c1830f7… / v1.2.0). A workflow_dispatch trigger is added so the scan can be run manually, and the docs are updated to describe the new wiring.
Changes:
- Add
actions/links(every event) andactions/scan(push/dispatch only,!cancelled()-guarded) as steps in theverifyjob, and add aworkflow_dispatchtrigger. - Delete the standalone
scan.yml(incl. its weeklyschedule) andlinks.ymlworkflows. - Update
docs/DISTRIBUTION.mdto reflect that the checks now run insideverifyand that secret coverage relies on GitHub native secret scanning for this public repo.
| File | Description |
|---|---|
.github/workflows/ci.yml |
Adds workflow_dispatch and runs the shared links/scan actions as final steps of the verify job. |
.github/workflows/scan.yml |
Removed; its secret/workflow scan (and weekly schedule) now lives in the verify job. |
.github/workflows/links.yml |
Removed; the Markdown link check now runs in the verify job. |
docs/DISTRIBUTION.md |
Documents the new in-verify link/scan steps and the public-repo secret-scanning posture. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
|
🎉 This PR is included in version 13.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |

Summary
The secret and workflow scan and the Markdown link check now run as the last steps of
Verify SDKinstead of in their own workflows..github/changes)mainactions/linksandactions/scanfrom putdotio/.github v1.2.0, pinned by commit. Links runs on every event; the scan passes through pull requests and runs on pushes and manual dispatch, which CI now accepts. The release job stays push-only.main: verify, the compatibility matrix, then semantic-release, which releases nothing for aci:commit.Verification
pnpm exec vp run verify,actionlint, andzizmorclean.Written by an agent (Claude Code, Claude Opus 5.5)