Skip to content

Refuse to build a public hub containing private repositories - #10

Merged
AdamXweb merged 1 commit into
mainfrom
fix/no-private-repos-in-public-hub
Aug 10, 2026
Merged

Refuse to build a public hub containing private repositories#10
AdamXweb merged 1 commit into
mainfrom
fix/no-private-repos-in-public-hub

Conversation

@adamXbot

@adamXbot adamXbot commented Aug 9, 2026

Copy link
Copy Markdown
Collaborator

A status hub lives in a public repository, so status.json is readable by anyone.

The first version tracked private repos there and withheld them from the badges and from STATUS.md. That is not sufficient: the source file itself named 25 private repositories across the three accounts, including unreleased products. Withholding them from the rendered output while listing them in the file defeats the purpose.

The build now fails if any entry has public: false.

Merge order

Merge the three data fixes first, or this guard will reject every hub:

Needs a v1 retag after merge, along with #9.

🤖 Generated with Claude Code

A hub lives in a public repository, so status.json is browsable by anyone. The
first version tracked private repos there and withheld them from the badges and
STATUS.md — but the source file named 25 unreleased projects across the three
accounts, which is exactly what the withholding existed to prevent.

Withholding a private repo from the rendered output is not enough. It must not
be in the file at all, so the build now fails on one.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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