TortoiseGit Credential Helper Validation Limits

Credential Helper Integration

TortoiseGit relies on the Git for Windows credential helper (such as manager-core or wincred) to delegate authentication to the Windows Credential Manager. While the TortoiseGit settings dialog allows the selection of a specific helper, the application does not directly manage the vault entries within Windows.

Behavioral Uncertainty

When Git for Windows is upgraded, the underlying helper binary may change or be renamed. TortoiseGit does not appear to validate the availability of the configured helper at startup, which can lead to authentication failures during remote operations if the helper name in settings no longer matches the installed binary.

Furthermore, while Git Credential Manager Core (GCM Core) supports advanced configurations like authority or tenant settings, these options are not exposed within the TortoiseGit user interface.

• Does TortoiseGit provide a mechanism to detect a missing or mismatched credential helper before a remote operation is attempted?
• Is there a way to configure GCM Core-specific tenant settings through TortoiseGit, or must these be managed via the global .gitconfig?