Skip to content

Navigation Menu

Sign in
Appearance settings
community
Sign in
Sign up
Appearance settings

@community GitHub Community

Discussion options

rickstaa
Jun 10, 2022

There is currently no way to fetch the languages a specific user uses. The current repositories/languages object of the GraphQL API will return the languages of a repository. I think allowing users to filter only the languages used in commits made by their user account would improve the GraphQL API. It would provide users with more accurate Language proficiency information and improve the stats displayed by repositories like github-readme-stats. I'm unsure if this is technically possible given the current GraphQL design and performance requirements and the linguist tool but here is my proposal.

Current behaviour

Current graphQL query:

query userInfo($login: String!) {
  user(login: $login) {
    repositories(ownerAffiliations: OWNER, isFork: true, first: 100) {
      nodes {
        name
        languages(first: 10, orderBy: {field: SIZE, direction: DESC}) {
          edges {
            size
            node {
              color
              name
            }
          }
        }
      }
    }
  }
}

Current GraphQL variables

{"login": "rickstaa"}

This will return the language stats per repository.

New behaviour

Maybe an attribute like isUser: true could be added for fetching user-specific language information.

New graphQL query:

query userInfo($login: String!) {
  user(login: $login) {
    repositories(ownerAffiliations: OWNER, isFork: true, first: 100) {
      nodes {
        name
        languages(first: 10, orderBy: {field: SIZE, direction: DESC}, isUser: true) {
          edges {
            size
            node {
              color
              name
            }
          }
        }
      }
    }
  }
}

New GraphQL variables

{"login": "rickstaa"}
You must be logged in to vote

Replies: 107 comments · 7 replies

Comment options

Olf0
Feb 9, 2023

I fully concur with the assessment and feature request: For many purposes the languages a user uses is of interest, not languages used in a repository. This data is currently not accessible via the GraphQL API!
You must be logged in to vote
0 replies
Comment options

StrangeRanger
May 3, 2023

I agree that this should be a feature.
You must be logged in to vote
0 replies
Comment options

jay23606
May 3, 2023

Another nice feature would be an easy way to get the most recent commit date when inside Tree entries:

https://www.reddit.com/r/graphql/comments/1338vwr/new_to_graphql_and_trying_to_understand_github/
You must be logged in to vote
0 replies
Comment options

Eminentzeal
Jun 10, 2023

I buy this idea because I do a lot of work as a contributor to organizations repository, that shoul reflect on my profile as well
You must be logged in to vote
0 replies
Comment options

Olf0
Jun 10, 2023

@Eminentzeal, please look at issue anuraghazra/github-readme-stats#1!
You must be logged in to vote
0 replies
Comment options

Temerold
Jun 17, 2023

👍 Agreed
You must be logged in to vote
1 reply
@Temerold
Comment options

Temerold Oct 26, 2023

I am voicing my support in an additional way.
Comment options

thatmare
Jun 22, 2023

I agree. I'm just learning to code and fork several projects to do so. After four projects and four months, the languages I used aren't in my top language stats. Any updates?
You must be logged in to vote
0 replies
Comment options

spacey-sooty
Sep 12, 2023

This would be super useful
You must be logged in to vote
0 replies
Comment options

QwEekYhyo
Sep 19, 2023

This should, indeed, be a feature.
You must be logged in to vote
0 replies
Comment options

Destroy666x
Sep 21, 2023

Forks are as important for GH as own repos, so definitely should be a thing.
You must be logged in to vote
2 replies
@Eagle3386

This comment was marked as spam.

Sign in to view
@Destroy666x
Comment options

Destroy666x Oct 25, 2023

@Eagle3386 sorry, but you show blatant ridiculousness here, spamming the whole comment section with way more useless repeated comment. People should be able to comment whatever they want under a feedback discussion. While "+1" type of comments are not too useful, you commented mostly on a bunch that added some point(s). I have no idea what encouraged you to stop us in a hypocritical and comedic way.

Also, do you realize:

  • you can turn email notifications off
  • you can unsubscribe from any discussions, knowing that 99% of replies in them will be support for the idea
    ?
Comment options

hokwanhung
Oct 3, 2023

I cannot agree more; it indeed will reflect more precisely and could allow counting for forks and other behaviours, especially when the repository is company-based and users are just collaborators.
You must be logged in to vote
0 replies
Comment options

BB-BenBridges
Oct 12, 2023

Thumbs up to this. My current stats look like I can only write Python but that is far from the truth as I use a large variety of languages but in company owned orgs.
You must be logged in to vote
4 replies
@Eagle3386

This comment was marked as spam.

Sign in to view
@BB-BenBridges
Comment options

BB-BenBridges Oct 25, 2023

Which I have done as well. Adding a further comment to show the different reasons this would be useful when this feature is developed could be useful to the devs. Certainly does not hurt.
@Eagle3386

This comment was marked as spam.

Sign in to view
@BB-BenBridges
Comment options

BB-BenBridges Oct 25, 2023

"new comments cause mails" - like the 10 emails I just got from you? 😄 It would be one thing if there were multiple new comments on this per day, but it's been fairly steady at one a week. If the mods disagree, they can delete comments and pin one asking only to up-vote and not comment.

Not trying to be aggressive as I can see you were just trying to help. Just trying to show you the slight hypocrisy in your comment. The mods of this repo can manage the notifications if its a big issue for them. Same goes for anyone subbed to this issue.
Comment options

CodedRedGIT
Oct 12, 2023

+1, this would be a super handy addition.
You must be logged in to vote
0 replies
Comment options

mb6ockatf
Dec 16, 2023

support this! 👍
You must be logged in to vote
0 replies
Comment options

aamehedi
Jan 15, 2024

Really need this 👍
You must be logged in to vote
0 replies
Comment options

gazer42
Aug 27, 2025

+1
You must be logged in to vote
0 replies
Comment options

jonathansilber
Sep 1, 2025

+1
You must be logged in to vote
0 replies
Comment options

UmiKami
Sep 25, 2025

+1
You must be logged in to vote
0 replies
Comment options

JustLikeCheese
Oct 10, 2025

+1
You must be logged in to vote
0 replies
Comment options

alt-0191
Nov 1, 2025

+1
You must be logged in to vote
0 replies
Comment options

filipopo
Nov 4, 2025

+1
You must be logged in to vote
0 replies
Comment options

sharktide
Nov 13, 2025

+1
You must be logged in to vote
0 replies
Comment options

it-me-joda
Nov 23, 2025

+1
You must be logged in to vote
0 replies
Comment options

mrinalTheCoder
Nov 24, 2025

+1
You must be logged in to vote
0 replies
Comment options

geniucker-dev
Dec 21, 2025

+1
You must be logged in to vote
0 replies
Comment options

onihilist
Dec 23, 2025

+1
You must be logged in to vote
0 replies
Comment options

nayrosk
Feb 9, 2026

+1
You must be logged in to vote
0 replies
Comment options

crafael23
Mar 11, 2026

+1
You must be logged in to vote
0 replies
Comment options

DereC4
Mar 27, 2026

+1
You must be logged in to vote
0 replies
Comment options

Othmane-ElAlami
Aug 26, 2026

+1
You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
other General topics and discussions that don't fit into other categories, but are related to GitHub Product Feedback Share your thoughts and suggestions on GitHub features and improvements
Morty Proxy This is a proxified and sanitized view of the page, visit original site.