Skip to content

Considering only commits made by myself #101

Open

Description

@zaaarf

Would it be possible? Specifically, only considering commits where the commit author is me. To my understanding, this currently does its maths on all full repositories, but I'm in a number of orgs that work in languages I'm absolutely unfamiliar with, so it's not really a fair representation of my actual skill. And yet, to manually ignore the orgs or repos would also cut out a significant part of stuff I actually did.

I'd implement this myself, but despite what the stats on my profile would have you believe, I'm not that proficient with Python.

(I'm aware what I'm using on my profile is a fork of this, but the problem exists on this one as well)

Activity

  1. changed the title [-]Considering only commits by myself[/-] [+]Considering only commits made by myself[/+] on Sep 18, 2023
  2. jstrieb commented on Sep 24, 2023

    @jstrieb
    Owner

    Hey @zaaarf, thanks for checking out the project!

    Yours is a reasonable question, and something I've thought a bit about. The short answer is that it seems to be more trouble than it's worth.

    It's already fairly annoying to get a list of all commits to a repo associated with a user (complicated by the fact that many users' Git commit emails don't correspond to their GitHub accounts). Extracting meaningful data about the files changed in each commit on top of that is significant additional complexity. It could probably be done by just using the GitHub API to get a list of repos, cloning them individually, checking out the relevant commits associated with a user, and using the GitHub Linguist tool to guess at languages. But to me, that's more trouble than it's worth for data of dubious accuracy.

    All that to say that it's definitely possible, just outside the scope of this little pair of scripts.

  3. zaaarf commented on Sep 24, 2023

    @zaaarf
    Author

    Hey @zaaarf, thanks for checking out the project!

    Yours is a reasonable question, and something I've thought a bit about. The short answer is that it seems to be more trouble than it's worth.

    It's already fairly annoying to get a list of all commits to a repo associated with a user (complicated by the fact that many users' Git commit emails don't correspond to their GitHub accounts). Extracting meaningful data about the files changed in each commit on top of that is significant additional complexity. It could probably be done by just using the GitHub API to get a list of repos, cloning them individually, checking out the relevant commits associated with a user, and using the GitHub Linguist tool to guess at languages. But to me, that's more trouble than it's worth for data of dubious accuracy.

    All that to say that it's definitely possible, just outside the scope of this little pair of scripts.

    I see. Would it be more doable, instead, to only count repositories where I have authored at least one commit? It still counts the whole repository, but it automatically filters out those I haven't worked in.

  4. jstrieb commented on Apr 19, 2026

    @jstrieb
    Owner

    Addressed by 6f25f02.

    That rewrite now only calculates stats for repos where you have authored one commit. It also adds support for calculating "lines changed" statistics by cloning the repo locally. (My hand was forced on the local clone by this incredibly frustrating issue.)

    Leaving this open in case you want to discuss further.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions