Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

How to interpret github clone stats

Tags:

github

On github you can view the traffic to your repository like so:

enter image description here

Now my question is about the huge discrepancy in clones and unique cloners. If I understand this correctly, it would mean that 4919 people have created 22.374 clones. Why would some people clone a repository so many times?

My actual repo looks a lot less impressive, but the discrepancy is still big. (About 30 unique clones for 150ish clones, so each cloner takes 5 clones).

That makes me wonder what is counting as a clone. If it's relevant, it's for a go library so I am assuming a go get counts as a clone, and go get -u possible for another one each time they update. But it'd surprise me if people were updating this much in a 2 week window.

like image 248
Dylan Meeus Avatar asked Jun 06 '19 23:06

Dylan Meeus


People also ask

How do I read insights on GitHub?

In the top right corner of GitHub.com, click your profile photo, then click Your organizations. Click the name of your organization. Under your organization name, click Insights. Optionally, in the upper-right corner of the page, choose to view data for the last 1 week, 1 month, or 1 year.

Can I see how many times my repo has been cloned?

For various reasons, GitHub repo owners need to track the number of times their code is downloaded or cloned. GitHub allows repository owners to track clone counts in a sliding window via the /graphs/traffic pane. However, GitHub does not track total counts.

Can you see who cloned your repo GitHub?

Can the owner of the repo see when someone clones it? No, they cannot.

How do I see my stats on GitHub?

You can try applying gitstats to a cloned repo of your GitHub repo. See also "Looking at Git Statistics", with the GitHub 'yearly_stats' for a simple little script. Pulse is a great way to discover recent activity on projects. You can find the link to the left of the nav bar.


1 Answers

I think the most likely explanation is the following:

both git-pull and git-clone actually call git-fetch under the hood, in addition to doing the work relevant to their commands.

see first couple paragraphs of each's manpages for explanations.

i doubt github tries to differentiate fetches that are part of a git-clone from ones that are simply appending an existing repo. (i'm not even sure that would be possible, haven't given it much thought)

From what I've read there is not much information on this floating around, so this is a really good question. And as @Bobulous says in his comment if it's not explained in the official documentation and blog posts you are most likely not going to find an objective answer on this question here. All we can do is speculate on what is going on underneath Github's hood.

In any case I recommend reading the following links that might help you find your answer:

  • The github stats on "clones":"unique cloners" seems heavily skewed, is "clone" actually "pull"?
  • Explain clones info in Github's Traffic tab
like image 134
Matthew Avatar answered Oct 01 '22 04:10

Matthew