ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #sourcetree
Goal Ensure that Sourcetree 4.0.1 uses a specific SSH key for Git operations when more than one key is available in the system’s SSH agent. Constraints The application does not expose a UI to choose the key, and the key used appears to be the first returned by the agent or the default key. This can cause failed pushes or pulls in environments with multiple i
When using Sourcetree’s Git Flow extension to finish a feature, the tool must decide which branch receives the merged changes. The expected behavior is that the feature branch is merged into the integration branch defined for the flow (commonly develop). However, if a repository has renamed its integration branch (e.g., using main instead of develop) or has
When working with repositories that exceed 100 k commits, SourceTree’s Log/History view appears to load commits incrementally, but the exact mechanics and limits of this pagination are not documented. The UI offers a Limit filter that caps the total number of commits retrieved, yet it does not provide a way to adjust the size of each incremental fetch or to
When a personal access token (PAT) used for HTTPS authentication in Atlassian Sourcetree expires, the application shows a generic Authentication failed dialog without indicating that the credential has expired. The goal is to determine whether Sourcetree can be configured or extended to surface a more specific error (token expired) so users can take timely a
Developers want to create repeatable, lightweight development environments by cloning repositories with a limited history depth directly from Sourcetree’s GUI. Currently the clone dialog only offers destination path and bookmark name, and there is no setting in global or repository preferences to define a default shallow‑clone depth. This forces users to fal
Sourcetree provides a visual repository browser with a side‑by‑side diff view and a commit graph that tracks branch history. The application also supports built‑in Git LFS integration and multiple Git accounts via SSH identity files or credential helpers. However, the UI does not clearly indicate when the current HEAD is detached, which can lead to confusion
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
SourceTree utilizes a proprietary interface for resolving Git merge conflicts, allowing users to select 'Mine' or 'Theirs' versions for individual files. When processing a commit tree containing hundreds of conflicted files, the application attempts to refresh the status of each item simultaneously within the UI. There is a documented inconsistency regarding
ssh
git