0

I am going to create a new github repo with the intention of forking a pre-existing public open-source project. Let's say the pre-existing project is https://github.com/foobarguru/foobar. Let's say I'm brec. Should my new repo be named foobar or something like foobar-brec? In other words should I use the same name (foobar) since access requires use of my name anyway and that sufficiently distinguishes the repo from the pre-existing one, or a distinct name?

brec
  • 259
  • 3
  • 10
  • If you fork it from GitHub's site it will create the repo for you. – vcsjones Dec 29 '11 at 21:02
  • @vcsjones. Thank you. It created the equivalent of [...]github.com/brec/foobar. That was the answer I was looking for. – brec Dec 30 '11 at 01:00

1 Answers1

1

2021:

To add to vcjones's comment, GitHub Fork help page does mention the only operation yu have to do is to click on that fork button:

fork button

The name of the forked (cloned on GitHub side for your account) repo will be the same than the original repo you have forked.

2022: the name of the fork... can differ from the original repository!

VonC
  • 1,262,500
  • 529
  • 4,410
  • 5,250
  • This is also the preferred way to fork a project on github, because this way github itself will mark the project as "fork", so everybody can see it (and -- I don't exactly -- as far as I know pull requests are only possible between forks). – KingCrunch Jan 02 '12 at 09:08