Stats and languages results incorrect due to graphql 100 records limit

[rickstaa]

Describe the bug

The current language and stats card results are incorrect for users with more than 100 repositories (see https://docs.github.com/en/graphql/overview/resource-limitations). This is because we are currently only fetching the first 100 repositories of a user account.

github-readme-stats/src/fetchers/stats-fetcher.js

Line 47 in a68abbb

repositories(first: 100, ownerAffiliations: OWNER, orderBy: {direction: DESC, field: STARGAZERS}) {

github-readme-stats/src/fetchers/top-languages-fetcher.js

Line 17 in a68abbb

repositories(ownerAffiliations: OWNER, isFork: false, first: 100) {

Because of this not all languages and stars of a user are represented.

Expected behaviour

I think we can use pagination options (i.e. cursor, after, endCursor objects) to loop through all repositories of a user account (see https://stackoverflow.com/a/70039506/8135687). @anuraghazra Let me know what you think.

TODOs

• Allow fetching of multiple pages for the languages data. fix: Fetch all repos for top languages #2111.
• Improve the stats card such that it fetches more pages when a user has more than 100 repositories with stars. fix: fetch all repos for for the stats card #2100
  • Merge feat: enable multi page star fetching for private vercel instances #2159 to make this available on private Vercel instances while giving us the control to disable it on the public instance because of rate-limiting problems.

[rickstaa]

For the language card, a PR is already open to solve this #1178. For the stats card, there not yet exists a pull request. This is, however, less important since only people with more than 100 repositories with stars are affected.

[lumynou5]

For the language card, a PR is already open to solve this #1178. For the stats card, there not yet exists a pull request. This is, however, less important since only people with more than 100 repositories with stars are affected.

Why it is less important? Although people with more than 100 repositories with stars are less.

[rickstaa]

@Luminous-Coder Thanks for your question. What I meant is that it is probably affecting fewer people. Since the GraphQL call we make returns the repositories listed from most starred to least starred, a user must have 100 repositories with many stars for to score to be significantly affected. I hope that clears things up. Nevertheless, we should solve both cases. 👍🏻

[MatteoPierro]

Hi @rickstaa, is it ok if I work on this for the stats card?

[rickstaa]

@MatteoPierro of course! That would be amazing. An example of how this can be done using pagination can be found here. I think for the stats card, to be resource efficient, I think we can stop the pagination when the GraphQL API does not return repositories that have any stars.