-
-
Notifications
You must be signed in to change notification settings - Fork 320
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Oxidise ‘git summary’ and ‘git summary —line’ #1742
Comments
To be clear, I mean including this in 'gix' or 'ein' directly |
Thanks for making me aware! Indeed I think all the functionality that's needed for a fast implementation of
However, in order to get ResearchFor completeness, here is the script's output when executed on the Git repository itself.
In comparison, here is the output of
With the
And with the
When using
I didn't take the time to let that finish, as it's clearly not made for more than a few hundred commits. |
Ok. That seems like it's 95% of the way there for me. I guess the only missing feature from git summary --line would be that ein doesn't appear to count remaining lines per author (I didn't spot that at least). That's kinda nice to know as if remaining lines is near to or actually zero you know that the author is inactive. Other than that it's mostly just small UX things for me. For example, I think it would be useful to have the list of authors in order of how much of the project they authored (ie sorted by number of commits or number of lines touched). Would you accept a PR to:
? |
Here is what
The data needed for this is already collected by With the right refactoring, I think |
Summary 💡
I.e https://github.com/tj/git-extras/blob/main/bin/git-summary
That’s a shell script and I imagine moving it to rust would be a significant performance bump. Particularly with ‘—line’ that can be kinda slow on large repos. Also as it appears to be using fairly standard git tools I’m supposing that everything might already in place (I noticed that GO just gained some support for blame), though TBH I haven’t done the due diligence so I’m not 100% sure.
If everything is in place I guess I could even take a crack at this myself if you agree to taking that feature in?
Motivation 🔦
Git summary is a nice tool to get an idea of the main contributors to an unknown repo. But it’s kinda slow for large repos
The text was updated successfully, but these errors were encountered: