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

SourceTree includes an Embedded Git engine so the application functions immediately after installation, while a System Git option lets the GUI use the operating system's Git binary. The choice is made in the application's Git options and applies per installation rather than rewriting repository-level configuration. However, switching engines does not automatically update global Git configuration, so credential helpers, signing keys, and external tool paths may need separate validation.

Because the bundled Embedded Git version and the system Git version can differ depending on the SourceTree release and operating system package cadence, it is unclear what concrete signals indicate that Embedded Git is genuinely insufficient. Some workflows, such as Git LFS or submodule operations, may behave differently under each engine, but the exact threshold where those differences become blocking is uncertain.

Which practical criteria should determine whether Embedded Git remains adequate for a given repository and hosting provider? What version comparison or workflow test reveals a real limitation without relying on assumptions about bundled versus system binaries? When is it safer to stay with Embedded Git despite a newer system version being available?