Skip to content

fix(ci): a sweep that sees fewer repos must say so - #44

Merged
catomean merged 1 commit into
masterfrom
fix/audit-private-visibility
Aug 26, 2026
Merged

fix(ci): a sweep that sees fewer repos must say so#44
catomean merged 1 commit into
masterfrom
fix/audit-private-visibility

Conversation

@catomean

Copy link
Copy Markdown
Collaborator

The first scheduled run inspected 32 repos; the same script locally inspected 34. The two missing were go-to-market and lifeops — private, and a workflow's default GITHUB_TOKEN is scoped to its own repo, so gh repo list returns only public ones.

Neither carries a model pin today, so nothing was missed. The problem is the shape of the failure: a sweep that quietly sees fewer repos than yesterday reports a cleaner fleet, not a smaller one — the same false ✓ the self-test exists to prevent one layer down.

It can't know the true count, but it can notice that not one private repo came back, which means either there are none or this token can't see them. Both deserve a line in the report. Set GH_TOKEN to a PAT with repo scope to cover them.

The daily run inspected 32 repos; the same script run locally inspected 34. The
two missing were `go-to-market` and `lifeops` — private, and a workflow's
default GITHUB_TOKEN is scoped to its own repo, so `gh repo list` returns only
public ones.

Neither carries a model pin today, so nothing was actually missed. The problem
is the shape of the failure: a sweep that quietly sees fewer repos than it did
yesterday reports a CLEANER fleet, not a smaller one, and that is the same
false ✓ the self-test exists to prevent one layer down.

It cannot know the true count, but it can notice that not one private repo came
back — which means either there are none, or this token cannot see them. Both
are worth a line. Set GH_TOKEN to a PAT with repo scope to cover them.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@catomean
catomean merged commit 16ff335 into master Aug 26, 2026
2 checks passed
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.

1 participant