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
I am trying to create a new repo and I keep getting "already has a repository with this name."
Yet I can't see it in the list or repositories or if I search via URL, I get URL not found.
Does it exist or is it a bug?
Welcome to the Atlassian Community!
Both. The bug (in my opinion) is that the error message is a bit unhelpful - it should be saying "there is already a repo with this name, but it is not one you have any access to view".
Because projects are a view, not a container. Your repositories need to have unique names to help people to distinguish between them.
I get it @Nic Brough -Adaptavist-, thanks for the reply, although still sounds like preference to me, not a thing that should be mandatory.
So to me the only solution I see would be to use different names like [public_html_01 ... 02] and after pull the updates, delete the original [public_html] folder and rename the folders back to [public_html] which is the root folder of Hostinger. Is that make any sense to you?
*Just a note here: We are talking about Private repositories. People shouldn't be looking for these...
I don't think it's a preferences problem, I think it's an identification problem, easily solved by having uniqueness.
Yes, you could use different names like that, or you could choose some other identifier. One of my clients simply prefixes the name of the service to it.