Skip to content
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

Blame via pygit2 instead of subprocess #127

Merged
merged 2 commits into from
Oct 10, 2023

Conversation

wetneb
Copy link
Contributor

@wetneb wetneb commented Sep 23, 2023

Closes #1.

As mentioned there, this seems to be much slower when run on large repositories, so I would not recommend merging as is. I'm curious if others have similar results.

This can be reconsidered if pygit2's blame algorithm improves.
The option can still be useful if the 'git' command is not available
on the system.
@wetneb wetneb marked this pull request as ready for review September 24, 2023 11:11
@wetneb
Copy link
Contributor Author

wetneb commented Sep 24, 2023

I added a toggle in the CLI to enable this, as suggested by @RonnyPfannschmidt. The refactoring that was needed for that will be useful for #62

Copy link
Owner

@aspiers aspiers left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Love it, thanks!!

@aspiers aspiers merged commit 89d51e8 into aspiers:master Oct 10, 2023
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

use pygit2's blame support
2 participants