Which SourceTree Git Engine Should Handle Current Authentication and Repository Features?

Short answer

Keep Embedded Git unless a side-by-side test shows it cannot complete a required repository operation. A newer system Git version is not, by itself, a reason to switch. The deciding evidence is identical fetch, push, LFS, submodule, and signed-commit checks run in SourceTree's built-in terminal under each engine.

Confirmed behavior

• SourceTree offers Embedded Git and System Git, selected in Tools > Options > Git per installation.
• Switching engines does not rewrite repository configuration or migrate global Git settings, credential helpers, signing keys, or external tool paths.
• Embedded Git bundles a known tool set, which can produce more consistent results across machines than System Git, whose behavior depends on the operating system PATH.
• System Git can expose OS credential helpers and keychain integration that Embedded Git may not see.

Likely explanation

Repeated authentication prompts after an engine change usually mean a credential helper configured for one engine is invisible to the other. Signed-commit failures often point to absolute GPG or signing-program paths that differ between engines. These are configuration mismatches, not evidence that one engine is inherently better.

Verification steps

1. In SourceTree, open Tools > Options > Git and record the active engine and reported Git version.
2. Open the built-in terminal for the target repository and run git version.
3. Run a fetch and push using the current authentication method and note any credential prompt.
4. Run git lfs pull if LFS is used, git submodule update --init if submodules are used, and create one signed commit if signing is required.
5. Switch to the other engine and repeat the same operations. A missing command, new auth prompt, or failure is a concrete limitation.

If both engines pass the same tests, stay with Embedded Git for reproducible team behavior. Switch only when the current engine provably lacks a required transport, credential path, or external tool.

Assumptions and uncertainty

This assumes a standard SourceTree installation with a functional bundled engine. The exact LFS and helper tools bundled with Embedded Git vary by release and operating system, so version numbers should be read from SourceTree rather than assumed. Current verification is required; treat this as a draft pending confirmation of your SourceTree version, operating system, and hosting provider.

Missing diagnostic detail: which authentication method the repository uses—HTTPS with a credential manager, SSH keys, or tokens—because that determines whether engine choice materially changes authentication behavior.