ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #sourcetree
SourceTree Commit History Loading Behavior SourceTree retrieves complete commit history using Git's native log commands without server-side pagination. When users navigate to branches containing thousands of commits, the application loads the entire history into memory and parses it locally before rendering the UI. This full result set retrieval can cause si
Sourcetree provides the option to toggle between the Embedded Git binary and the System Git installation via the Tools > Options menu. This configuration determines whether the application uses a bundled version of the Git CLI or the version installed globally on the operating system. When transitioning from System Git to Embedded Git, there is a risk of
Git Operations Retry Handling in SourceTree SourceTree relies on Git's native retry mechanisms for network operations rather than implementing its own retry logic. When performing fetch, pull, or push operations, the client delegates retry handling to Git's built-in credential caching and retry capabilities. The behavior is controlled through git config para
Goal: ensure that after a remote fetch, Sourcetree's displayed ahead/behind counts reflect the latest state without requiring a manual refresh. Uncertainty: the internal cache of remote branch references may remain stale until a user-initiated refresh (F5 or Repository -> Refresh) is performed, and there is no documented option to change this behavior. Qu
Goal I want low-noise alerts from SourceTree on desktop: a single OS notification only when something high-value happens, such as a failed pull or a commit landing on a protected branch, with everything else going to a local log file. Constraints My understanding is that SourceTree Custom Actions are user-invoked menu items rather than an always-on event sys
git