GPT-5 finding
Live fallback pagination emits multiple JSON arrays (invalid aggregate) with gh api --paginate + array-wrapping --jq
highbughigh
- skills/fork-first-run-alert/SKILL.md:118-122
With gh api --paginate, each page’s response is processed by --jq independently and printed sequentially. Using an array-wrapping jq program ('[.[] | ...]') produces one array per page, printed one-after-another. Redirecting that into /tmp/forks.json yields concatenated arrays, which is not valid JSON and not a single combined list. Any downstream logic expecting a JSON array will fail to parse or silently drop pages, causing missed forks and false negatives in activation detection.
Recommendation
Aggregate paginated items as a single list. Options: - Emit items line-by-line and slurp into an array: gh api "repos/${PARENT_REPO}/forks" --paginate --jq '.[] | select(.archived != true and .disabled != true) | {full_name, owner: .owner.login, stargazers_count, created_at, pushed_at}' | jq -s 'sort_by(.pushed_at) | reverse | .[:80]' > /tmp/forks.json - Or, drop --jq and pipe to jq -s 'add | ...' to merge arrays. Ensure the final file is a single valid JSON array, sorted and trimmed as specified.