Skip to content

Conversation

@DefaultRyan
Copy link
Member

No description provided.

Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This PR attempts to remove the LibGit2Sharp NuGet package dependency from the FileExplorerGitIntegration project. However, the removal is incomplete as the codebase still extensively uses LibGit2Sharp types and imports.

Key Changes:

  • Removes LibGit2Sharp version 0.30.0 from package references

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.


<ItemGroup>
<PackageReference Include="LibGit2Sharp" Version="0.30.0" />
<PackageReference Include="Microsoft.Windows.CsWin32" Version="0.3.106" />
Copy link

Copilot AI Dec 20, 2025

Choose a reason for hiding this comment

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

Removing the LibGit2Sharp package reference will cause compilation errors. The codebase still has multiple references to LibGit2Sharp types that are not defined elsewhere:

  1. Files still importing LibGit2Sharp:

    • Models/GitRepositoryStatus.cs (line 4)
    • Models/GitStatusEntry.cs (line 6)
    • Models/RepositoryWrapper.cs (line 6)
    • Models/StatusCache.cs (line 7)
  2. LibGit2Sharp types still in use:

    • FileStatus enum: Used extensively in GitRepositoryStatus.cs, GitStatusEntry.cs, RepositoryWrapper.cs, and StatusCache.cs
    • SubmoduleStatus enum: Used in GitRepositoryStatus.cs, RepositoryWrapper.cs, and StatusCache.cs

Before removing this dependency, you need to either:

  • Define custom FileStatus and SubmoduleStatus enums to replace the LibGit2Sharp types
  • Remove all code that depends on these types
  • Replace the LibGit2Sharp implementation with an alternative approach

Copilot uses AI. Check for mistakes.
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.

2 participants