You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Download watchers, forks, and stargazers of a repo #192
I would like to move away from GitHub at some point, but also would like to keep data around who starred my repos, who was watching it, and who forked it.
The existing flags only capture the outbound direction: --starred (repos you starred), --watched (repos you watch), --followers/--following (people). Nothing captures the inbound social graph of a repo you own. --fork is unrelated too, it controls whether your own forks get cloned, not who forked you.
Regular repositories also get no metadata JSON written at all. backup_repositories only dumps gist.json for gists, so the repo API object (which carries stargazers_count, forks_count and subscribers_count) is used in memory and discarded. So today you can't recover even the counts after the fact, let alone the identities.
Adding it would mean three paginated endpoints:
GET /repos/{owner}/{repo}/stargazers
GET /repos/{owner}/{repo}/subscribers, which are the actual watchers; watchers_count in the repo object is a legacy alias for the star count
GET /repos/{owner}/{repo}/forks
It's a nicely self-contained piece of work if you or anyone else reading this fancies picking it up, PRs very welcome. Given the issue has been sitting a while, is this still something you need? Happy either way, just useful to know whether to leave it open for someone to grab.
Activity
Iamrodos commentedon Jul 26, 2026
Still unimplemented as of 0.63.0.
The existing flags only capture the outbound direction:
--starred(repos you starred),--watched(repos you watch),--followers/--following(people). Nothing captures the inbound social graph of a repo you own.--forkis unrelated too, it controls whether your own forks get cloned, not who forked you.Regular repositories also get no metadata JSON written at all.
backup_repositoriesonly dumpsgist.jsonfor gists, so the repo API object (which carriesstargazers_count,forks_countandsubscribers_count) is used in memory and discarded. So today you can't recover even the counts after the fact, let alone the identities.Adding it would mean three paginated endpoints:
GET /repos/{owner}/{repo}/stargazersGET /repos/{owner}/{repo}/subscribers, which are the actual watchers;watchers_countin the repo object is a legacy alias for the star countGET /repos/{owner}/{repo}/forksIt's a nicely self-contained piece of work if you or anyone else reading this fancies picking it up, PRs very welcome. Given the issue has been sitting a while, is this still something you need? Happy either way, just useful to know whether to leave it open for someone to grab.