Working on a feature, spot a piece of dead code, take me 5 seconds to remove and commit it. But it's not related to my feature.
Could remove & stash, but over the course of a feature, stash list can become quite long, and when working with a team, there might be frequent overlap. A shared, repos-based stash wouldn't help there because stashes aren't supposed to conflict.
So what I'm left with is the notion of having a "cleanup" workflow/branch, and as individuals work from ReleaseX branches, they can fire-off their cleanup touches like this to ReleaseX-cleanup.
Is such a thing possible with SourceTree? Commit to another branch (even if its very limited, still useful)?
Not really possible in Git, so not possible in SourceTree. You would need to switch to the other branch when you don't have anything else uncommitted (and hope that the file you modified is otherwise the same between the two branches), commit that file, then switch back.
Supported Platforms macOS Windows To make using Sourcetree as simple yet powerful as possible we embed (bundle) dependencies such as Git, Git LFS, and Mercurial. We strive to keep these...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs