#128 √ resolved
Alex Coles

Cannot fork a repository with the same name as an existing repository.

Reported by Alex Coles | April 4th, 2008 @ 02:10 PM

There is an namespacing-conflict when trying to a fork a public

repository that has the same name as an existing repository that I own.

Scenario:

  • I have an existing repository (private, in this case) named

"myrepo".

  • I want to fork someone else's public repository, also named

"myrepo".

  • They happen to be unrelated projects, or at least projects of a

separate origin - It just happens that I just want to work on them both.

What actually happens:

  • When you try to fork someone else's public repository, the forking

fails, and instead you're redirected to your existing repository of

the same name.

What I'd like to happen:

EITHER:

  • To be able to rename repositories (see also ticket #75).
  • To be prompted to rename either your existing repository, or your

forked repository.

OR (less preferable, but better than nothing)

  • for, GitHub to automatically give the forked repository a

different, non-conflicting name (e.g. "myrepo1", "myrepofork", "myrepo-

abc").

(P.S. this isn't a hypothetical! I am actually having this problem.)

Comments and changes to this ticket

Please Login or create a free account to add a new comment.

You can update this ticket by sending an email to from your email client. (help)

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

Shared Ticket Bins

People watching this ticket