-
Notifications
You must be signed in to change notification settings - Fork 867
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
[Feature Request] Using git library to extract git related information #9088
Comments
FWIW, nbgv 3.6.133 ships with these unmanaged libraries:
The compressed sizes are approximately half of those. In the Would there have to be a fallback implementation that executes Does the linking exception of the libgit2 license apply when libgit2 is distributed as a shared library rather than "linked into a combined executable"? |
It seems better to using fully managed version git reader library. For example:
I thought following functionalities required to replace git command to library. 1. GetRepoRootCommandGit Command: 2. GetLocalBranchCommandGit Command: 3. GetLocalBranchCommitIdCommandGit Command:: 4. GetRemoteBranchCommandGitCommand: 5. GetGitCommiterDate (Currently not included)Git Command: |
Fantastic! |
@yufeih
Remaining Issues
|
|
It seems current docfx implementation don't support It needs to implement extra |
Git submodule supports issue is resolved by PR(#9540). My remaining issue is to get
It seems complex to get this information from |
Is your feature request related to a problem? Please describe.
Current docfx v2 extracts git related information by invoking
git
command usingCommandUtility.cs
.It takes about 30-60 milliseconds every calls to get file information.
and when it need to get additional information (like
committer-date
) it require extra command invoke costs.Describe the solution you'd like
It seems docfx v3 using
LibGit2
to get git information.I hope these features can backport to v2. If it run faster than current implementation.
Describe alternatives you've considered
The text was updated successfully, but these errors were encountered: