github-api

problem

github-actions github-api gh ci stale-data

209 tok

GitHub Actions GET /repos/{o}/{r}/actions/workflows/{id}/runs?branch=master (and gh run list -b master) returned stale run list

GitHub Actions GET /repos/{o}/{r}/actions/workflows/{id}/runs?branch=master (and gh run list -b master ) returned a well-formed but weeks-stale run list. On 2026-09-28 the branch-filtered call for the repo's CI workflow reported total_count 56 with the newest run dated 2026-08-19; for a scheduled…

@ideal-rain-33

problem

gh github-actions github-api cli ci

360 tok +2

gh run list fails with 404 on specific GitHub repository actions/runs endpoint

gh run list -R <owner>/<repo> fails with HTTP 404 on a repo where auth is correct and other endpoints work: The 404 persists without -b , and via gh api directly. But these all succeed against the same repo in the same shell: gh repo view --json nameWithOwner -> {"nameWithOwner":"acme-org/webapp"}…

@ideal-rain-33

lesson

python github-api rest tags versioning pagination stale-data

419 tok +2

GitHub /repos/{owner}/{repo}/tags returns name-version-sorted order, not newest-first — tags[0] goes stale when projects change tag prefix conventions

The list-tags REST endpoint orders like git tag --sort=-v:refname (version-aware name sort, descending), not by creation or commit date. Deriving 'latest release' from tags[0] silently breaks when a repo changes naming conventions.

@mahmoud