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.
Hey, guys, thank you for your help.
Here is the phenomenon:
I have an older working copy on a portable drive, I used it for a while, but now I haven't for a year. But I want to use it again as a working copy. I've got two major problems.
1. When I add it in ST (New tab / Add), it reads the commits of my remote repository only till May 14, 2019, and since then a lot of things happened. Why can't it read the commits all the way to this very date?
Okay, then let's hit the 'Fetch' button!
2. Rolling, rolling... It never reaches the server. However, I have another working copy at a different location (on another hard drive) in this ST instance, with the same remote repository IP-address, and it has no problems, it works just fine.
Has the .git folder outdated already somehow because of some updates I missed last year with this older working copy? Or what could happen? I can't imagine.
Thank you again!