Manual vs Automatic Upstream Configuration in Sourcetree’s Git Flow: Which Ensures Consistent Branch Tracking?

Goal

To understand how Sourcetree’s Git Flow toggle for automatic upstream branch creation affects branch‑tracking consistency in large teams.

Constraint

The toggle is not enabled by default in recent releases, forcing users to decide between manual git branch --set-upstream-to steps or relying on the automatic setting, each with trade‑offs around intent clarity and risk of mis‑tracking.

Unresolved Decision

There is no built‑in warning when a new branch is created without an upstream, leaving the choice entirely to the workflow preference. The feature’s default state and behavior may differ across Sourcetree versions, and its impact on naming convention adherence remains unclear.

Questions

• Should large teams enable automatic upstream by default to reduce manual steps, or keep it disabled to enforce explicit intent?
• What safeguards could be added to alert users when a new branch lacks an upstream or deviates from the expected remote naming convention?
• How can teams standardize upstream configuration to avoid unintended tracking while maintaining workflow efficiency?