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!


What happens with the repository's old remote url when moving a repository to another project?


Within the repository settings, there is an option to move the repository to another project. (Repository Settings -> Move Repository -> Selecting another project -> clicking move).

After moving the project, local copies of this git repository still seem to be able to push , pull and even clone the project using the old clone URL.

For how long will this old remote URL still work? A day? "For ever"? Just as long as there is not another project created with the same  (old) clone url?

1 answer

I came here wondering the same. Since the feature doesn't seem to be explicit, I would guess the old remote URL redirects are kept as best effort, but not guaranteed for any length of time. Probably to help smooth over the transition from the old repo name to the new, but nothing more.

It's been a few years. How did the old clone URLs hold up for yours?

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events