This repository was archived by the owner on Jun 29, 2026. It is now read-only.
fix(ci): use correct gh search JSON field names in regenerate#2
Open
0xbrayo wants to merge 1 commit into
Open
Conversation
gh search repos uses fullName/stargazersCount/language, not the GraphQL-style nameWithOwner/stargazerCount/primaryLanguage names. The mismatch made every topic query exit non-zero, so the registry regenerated with zero entries (no repos, including tagged skills, were ever discovered). Switch to the supported field names, derive type badges from the matched search topics (repositoryTopics isn't available via search), and aggregate multiple topics per repo.
Member
Author
|
@TimeToBuildBob review |
TimeToBuildBob
approved these changes
Jun 24, 2026
TimeToBuildBob
left a comment
TimeToBuildBob
left a comment
Member
There was a problem hiding this comment.
The diff looks correct — the old JSON field names (nameWithOwner, stargazerCount, primaryLanguage, repositoryTopics) don't match what gh search actually outputs. The new fields (fullName, stargazersCount, language) are the real API field names, and the _topics accumulative approach correctly handles repos matching multiple registry topics.
Also good: dedup by fullName is consistent with the new field name, and the removed extract_topics helper was dead code after the schema change. LGTM.
Member
Author
|
merge the PR |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
gh search repos uses fullName/stargazersCount/language, not the GraphQL-style nameWithOwner/stargazerCount/primaryLanguage names. The mismatch made every topic query exit non-zero, so the registry regenerated with zero entries (no repos, including tagged skills, were ever discovered).
Switch to the supported field names, derive type badges from the matched search topics (repositoryTopics isn't available via search), and aggregate multiple topics per repo.