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
Next: Root
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'm getting the above noted error when attempting to sync from a remote repository of mine. Using Sourcetree Mac 2.7.6. Not sure what to do about that.
Can I just delete that local repository and then choose to Clone it on the Remote tab of Sourcetree?
I just checked the remote repository and see the .hgtags file there, so I assume that means the most recent Push was done with the default branch checked out, which, as I said above, is the only branch that has an .hgtags file when checked out (the develop branch doesn't).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok. Now I can successfully Pull on the problem computer noted initially. What I did was create another changeset on the Pushing computer and Pushed it. Now it all works okay on the Pulling computer. I'd still love to know why this happened at all, though.
But I do notice that in all three repositories (remote repo and the 2 local repos) I have an .htags file in their default branch and not in their develop branch. Is this a problem? If so, how do I correct it?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I notice in the computer that did the upload to the remote repository, there's an .hgtags file there when the default branch is checked out, but not when the develop branch is checked out. Is that a problem? I usually do a Push from that computer with the develop branch checked out.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.