ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #tortoisegit
Configuration transition TortoiseGit delegates HTTPS operations to the configured Git for Windows installation, which selects a TLS backend via http.sslBackend . Recent Git for Windows releases default to Schannel on Windows, while older bundled versions used OpenSSL with a curated CA bundle. This transition alters which root certificates are trusted during
Browsing a large Git working tree in File Explorer with TortoiseGit overlay icons enabled can produce sustained growth in the Windows shell process private working set. The documented failure condition points to the shell extension's recursive status cache rather than Git itself, particularly when the cache tracks a broad set of paths under default monitorin
TortoiseGitNotify raises Windows toast alerts when file status changes are detected within a repository's watched path. A persistent design tension exists between surfacing meaningful changes and avoiding alert fatigue from untracked, ignored, or submodule-internal events. The feature set includes checkboxes to disable notifications for untracked files and w
A Windows workstation authenticates to a Git remote over SSH without issues when using TortoiseGit, but the same repository and credentials fail on a production or CI machine. The suspected boundary is the SSH client configured under TortoiseGit Settings > Network > SSH client. By default TortoiseGit ships TortoiseGitPlink, a PuTTY derivative that expe
Goal: achieve consistent, non-blocking commit-log navigation when invoking TortoiseGit Show Log from Windows Explorer on large repositories, ensuring that the incremental loading behavior aligns with the underlying Git revision-range retrieval without exposing pagination controls to the user. Constraints: TortoiseGit currently loads commits in batches as the
TortoiseGit's icon overlays serve as the primary at-a-glance alert layer for modified, conflicted, or unversioned files, configured under Settings -> Icon Overlays. The Status cache setting offers Default, Shell, Shell extended, and None, but the documentation does not prescribe a single correct value. Moving from the Default cache to the Shell cache shif
Goal I want a predictable way to manage ignore rules from TortoiseGit's context menu so that files ignored via the GUI behave identically to files ignored by editing .gitignore from the Git CLI. The two components involved are the TortoiseGit Windows Shell Extension and the Git for Windows binary it wraps (TortoiseGit 2.x with a current Git for Windows insta
TortoiseGit executes long-running operations such as fetch, push, and clone through a dedicated progress dialog. When a user manually triggers the 'Cancel' action during these operations, the UI's behavior depends on the configuration settings found under Settings > Dialogs 2. There is an uncertainty regarding how the application distinguishes between an
TortoiseGit stores Git credentials in the Windows Credential Manager and reuses them for subsequent operations without checking their validity. The goal is to prevent repeated authentication failures caused by expired or revoked tokens while preserving offline usability. However, it is unclear whether TortoiseGit should automatically validate credential expi
ssh
git