Which Git executable should Sourcetree use by default for feature parity and stability?

Sourcetree allows users to select between its bundled Git executable and the system-installed Git via Tools → Options → General, but Atlassian provides no definitive guidance on which choice best balances access to newer Git features against operational stability. The bundled Git in Sourcetree 4.x typically trails upstream releases by several versions, meaning capabilities such as experimental hash algorithms, performance improvements, or updated protocol support may be unavailable. Conversely, pointing Sourcetree at the system Git introduces variability: on Windows the system Git may come from Git for Windows, WSL, or a custom path, and its version can be outdated, missing, or configured with non-standard hooks that alter command behavior.

Switching the Git executable after repositories have been opened can change how commands like submodule updates, LFS filter processes, or merge strategies execute, potentially causing silent failures or inconsistent results across team members who have made different selections.

Does Sourcetree's bundled Git receive security backports promptly enough to justify staying on it? Which specific Git versions have been validated against each Sourcetree release? What criteria should teams use to decide between bundled and system Git in a mixed-environment workflow?