Conversation
Pings each entry in data/repos.json against the GitHub API every Monday 09:00 UTC. If any return 404 (owner or repo deleted), are flagged archived, or flagged disabled, opens or updates a single [Audit] tracking issue listing them. Why: PR #107 made lib/github.js fail-loud on GraphQL NOT_FOUND so build-pages no longer commits empty pages. Side effect: one deleted third-party repo blocks the entire build pipeline silently. The Web3CZ/Web3Hermes incident on 2026-05-01 burned 2+ days of failed build-pages runs before triage caught it. This audit surfaces dead entries proactively so a maintainer can remove them before the next build breaks. Idempotent: reuses the existing open [Audit] issue and just updates title/body if the set of flagged repos changes week-over-week. Cost: ~110 authenticated REST calls per Monday — well within rate limits, completes in <30s. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
New
.github/workflows/audit-repos.yml— weekly cron (Mondays 09:00 UTC) that pings each entry indata/repos.jsonagainst the GitHub API and detects:If any are found, opens or updates a single
[Audit]tracking issue listing them. Idempotent across runs (reuses the existing open audit issue).Why
PR #107 made
lib/github.jsfail-loud on GraphQLNOT_FOUNDsobuild-pagesno longer silently commits empty pages — the right call. Side effect: one deleted third-party repo blocks the entire build pipeline, and there's no proactive monitor.The
Web3CZ/Web3Hermesincident on 2026-05-01 burned 2+ days of failedbuild-pagesruns (4/30 cron, 5/1 cron, every merge-triggered run for #79, #146, #147) before triage caught it. By that point all 12 newly-added repos were silently absent from the live site.This audit surfaces dead entries proactively so a maintainer can remove them before the next build breaks.
Cost
~110 authenticated REST calls per Monday. Well within rate limits (5,000/hr authenticated). Completes in <30s.
Companion changes
repo-auditlabel on the repo so the workflow has somewhere to attach the issue.Test plan
workflow_dispatchto test manually — should report 0 dead/archived/disabled (we just removed Web3CZ in Remove dead Web3CZ/Web3Hermes entry — unblocks build-pages #148; nothing else known dead)🤖 Generated with Claude Code