You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I have a base branch "working".
Now I create a branch "/bug/mix/fix_bug_of_program" and make it track working.
Then I change some file, pull from working, commit change and push it to remote branch "/bug/mix/fix_bug_of_program"
Then I check and it lost track to working (when pull, it so remote branch to pull is "/bug/mix/fix_bug_of_program" instead of "working", and when right click/ track remote branch it has no tick in origin/working)
So how to prevent Sourcetree from losing tracked branch after pushing?
If you push local branch "/bug/mix/fix_bug_of_program" to remote branch "/bug/mix/fix_bug_of_program" then you have changed the tracking from
"/bug/mix/fix_bug_of_program" -> "/bug/mix/fix_bug_of_program"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.