Skip to content

chore(ci): remove temporary print-findings scaffolding from scan wrapper - #551

Merged
hyperpolymath merged 1 commit into
mainfrom
claude/remove-scan-scaffolding
Jun 26, 2026
Merged

chore(ci): remove temporary print-findings scaffolding from scan wrapper#551
hyperpolymath merged 1 commit into
mainfrom
claude/remove-scan-scaffolding

Conversation

@hyperpolymath

Copy link
Copy Markdown
Owner

What

Removes the print-findings job from .github/workflows/hypatia-scan.yml, restoring the wrapper to its thin form (hypatia: job + secrets: inherit).

Why

That job was triage scaffolding — it downloaded the hypatia-scan-findings artifact and cat'd hypatia-findings.json to the job log so the self-scan findings could be enumerated without artifact download. Its own comment says "TEMPORARY (triage scaffolding — remove before merge)", but it shipped to main with #545. It adds a redundant download-and-print job to every scan run.

The findings are still fully available via the hypatia-scan-findings artifact uploaded by the reusable workflow (if: always()), so nothing is lost.

No change to the scan itself or the e2ef79ee reusable pin.

🤖 Generated with Claude Code


Generated by Claude Code

The print-findings job was triage scaffolding (it cat'd the uploaded
hypatia-findings.json to the job log to enumerate self-scan findings without
artifact download). It was marked "remove before merge" but shipped to main
with #545. Restore the wrapper to its thin form: the scan job + secrets:
inherit only. Findings remain available via the hypatia-scan-findings
artifact uploaded by the reusable.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01V13sGvHnaeCY5A9fF2QsDm
@hyperpolymath
hyperpolymath marked this pull request as ready for review June 26, 2026 21:49
@hyperpolymath
hyperpolymath merged commit 84cee95 into main Jun 26, 2026
35 of 37 checks passed
@hyperpolymath
hyperpolymath deleted the claude/remove-scan-scaffolding branch June 26, 2026 21:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants