Remove dead Web3CZ/Web3Hermes entry — unblocks build-pages#148
Merged
Conversation
The Web3CZ user account no longer exists on GitHub (HTTP 404 on both the repo and the user). PR #107's fail-loud GraphQL handling correctly surfaced this — build-pages.yml has been failing for at least 2 days (4/30 daily cron + every merge-triggered run since) because lib/github.js throws on the NOT_FOUND, blocking the entire 112-repo metadata fetch. Removing the entry unblocks the rebuild. As of this commit, all 12 new repos added during today's triage (PRs #79, #146, #147) will start appearing on hermesatlas.com. Should also kick off a periodic dead-repo detector so this doesn't recur silently — left as a follow-up. 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 was referenced May 1, 2026
ksimback
added a commit
that referenced
this pull request
May 1, 2026
After generating project pages, scan projects/ for any *.html whose
{owner}/{repo} no longer appears in repos.json and delete it. Also
removes the owner directory if it ends up empty.
Without this, removing a repo from data/repos.json leaves a stale
project page on the live site indefinitely. Concretely: Web3CZ/Web3Hermes
was removed from repos.json in PR #148 (account deleted on GitHub),
but hermesatlas.com/projects/Web3CZ/Web3Hermes still serves the
pre-removal HTML because Vercel hosts the committed file as static
content. The next build-pages run after this lands will clean it up
automatically.
Safe by construction: only deletes files within projects/{owner}/*.html
that are not in the canonical repos.json list. Local dev runs are fine
— stale pages from prior local-only experimentation get garbage-
collected too.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
Removes the
Web3CZ/Web3Hermesentry fromdata/repos.json. The Web3CZ user account is gone from GitHub entirely — bothhttps://github.com/Web3CZ/Web3Hermesandhttps://github.com/Web3CZreturn HTTP 404.Why this is urgent
PR #107's fail-loud GraphQL handling correctly surfaced the issue, but it's been blocking every
build-pagesrun for at least 2 days:Net effect: all 12 community repos added during today's triage are sitting in
data/repos.jsonbut not yet rendered as project pages on hermesatlas.com. This unblocks them.Follow-up
Should add a periodic "dead repo detector" so this doesn't recur silently. Either:
audit-summaries.ymlweekly cron to alsoHEAD-check each entry's GitHub URLlib/github.jslog+skip NOT_FOUND repos with a warning instead of throwing (less safe — silent corruption risk)I'd lean toward the first.
Test plan
/projects/{owner}/{repo}for the 12 today-added repos🤖 Generated with Claude Code