Description Christian Halstrick 2011-07-06 07:55:56 EDT

When you use JGit PushCommand and you don't specify an explicit refspec then JGit uses implicitly a refspec which potentially leads to the creation of a new branch in the remote system. The new branch will have the same name as the currently checked out branch.

Here JGit behaves differently from native git, where a push without an explicit refspec leads to the update of all "matching" branches (branches which exists locally and remotely). A native git push would not create new branches.

My problem is that JGit under the hood (without an explicit refespec) takes my local branch names to create branches on the remote system. Up to know I was sure that I can name my branches as I like (tmp1, tmp2, f***ingBugFix, ...) because I knew that J/EGit will never publish these names without my explicit order. That's not true anymore.

My proposal: If we can't have these "update only matching branches" rule then we should simply not update/create any branches if user "forgot" to specify any refspec.