Git in PhpStorm - How to create fork? Follow Evgeniy Created January 31, 2011 18:10 I'm newbie in GitHub.Tell me please, how to make fork in existing project inside PhpStorm.
Actually there are 2 diffrerent approaches for forking someone else's repo. If you need only read access to the repo you should just click "watch" using github web UI and this repository will be available in clone project action dialog. Please have a look at the blogpost dedicated to github integration for IntelliJ platform based IDEs: http://blogs.jetbrains.com/idea/2010/10/github-integration-in-intellij-idea-base-features/
In case if you need to have full featured readwrite acess you should "fork" the project from github web UI and you'll get a forked one among your own repositories. They you can checkout it the same way.
It's my code, my project.
I decide to create fork, because I want to change code, and it can make it unstable :)
So, I want to save "master" branch and experiments in new branch.
With Git GUI (yes, I'm Windows user) I finally had made new branch.
After restarting PhpStorm, new name of branch become in status bar, that's fine. But now I can't make commits:
"failed to push".
In case if you created your own branch locally it is pretty natural that push attemp fails. At first you should create corresponding remote branch and configure your own to push to.
It is nescessary to note that local branches has nothing to do with the "fork on github" term.
"corresponding remote branch" was created automatically, I can see it in github web-ui.
What should I "press", to configure? Please, write steps. Sorry, if I'm taking your time.
Well... So, how can I work with created fork?
В данный момент ничего не понятно.
I wrote, that I created a new branch by the Git GUI - this tool can push branch into the repository.
So, your suggestion about "pretty natural that push attempt fails" is wrong.
My mistake was in name of branch - I should use "origin/[NameOfBranch]" instead of "[NameOfBranch]". But it is GitHub idiotic rule, nobody else (they are agree with me, read there).
So, if somebody else will got same case, simple solution is:
Yes, I see, thanks a lot for publishing workaround :)