You have to give it some name. If HEAD creates the same name as the local
branch on the remote side, great. More than one way to do the same thing.


On Mon, Mar 4, 2013 at 1:57 PM, sgilda <notifications@github.com> wrote:

> In CONTRIBUTING.md:
>
> >
> > -9. Browse to the <topic-branch-name> branch on your forked Git repository and [open a Pull Request](http://help.github.com/send-pull-requests/). Give it a clear title and description.
> > +        git push origin HEAD
> > +   _Note: The above command assumes your remote repository is named 'origin'. You can verify your forked remote repository name using the command `git remote -v`_.
> > +11. Browse to the <topic-branch-name> branch on your forked Git repository and [open a Pull Request](http://help.github.com/send-pull-requests/). Give it a clear title and description.
>
> @LightGuard <https://github.com/LightGuard> : When I test changes on my
> own branch, I always use HEAD and it creates a branch on my remote
> repository with the same name as my local branch. I looked back through
> chat logs and found I got this command from @pmuir<https://github.com/pmuir>originally.
>
> I actually didn't change this line. It just got moved down from line 50
> above when I inserted more information about git add, git status, and
> commits. :-)
>
> Do you not need the HEAD?
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/jboss-jdf/jboss-as-quickstart/pull/462/files#r3232192>
> .
>



-- 
Jason Porter
http://en.gravatar.com/lightguardjp