Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Can only push to a feature branch once, then it disappears. Maybe related to clone depth being set.

I have a repo I've taken on where I had to set the clone depth to 1 in SourceTree as it wouldn't clone the entire repo (would error every attempt). I was able to clone the repo with GitKraken without changing the depth, but the repo is private and I only have the free version of GitKraken.

Making the assumption that the clone depth is the cause, when I create a feature off the develop branch I can push once to said feature and then it's no longer listed as a branch to push to. Master and develop are still listed, but not the feature. I can see the feature branch in BitBucket. Fetching from origin also doesn't list the feature.

The only work around I've found is to finish the feature (yes, I can finish it) then re-create the same named feature and push to that. If I stage changes and commit them to push, I cannot then see those changes once committed and not able to push either.

If it is because the depth is set to 1 (no other repo does this), is there a way to change the repo depth now that I have the most recent commit? Assuming there's less to pull down.

1 answer

Thinking about it, the clone depth was only the initial clone. All the history is being listed since that point.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events