| EGit (or maybe JGit) checks out the wrong branch [message #789057]
||Thu, 02 February 2012 14:58
| Matthew Webber
Registered: December 2010
A repository on GitHub has a default branch of "master", but when I check it out using EGit/JGit, it checks out a branch called "1.0". If I "git clone" using the command line, it checks out the "master" branch as expected.|
Here's how to reproduce the problem:
- In the "Git Repsoitories" view, I click on "Clone a Git repository and add the clone to this view". I enter the URI (git://github.com/DawnScience/dawn-edna.git in this case).
- I click "Next", it shows me the branches on the remote.
- I click "Next", where I can select the initial branch.
The problem here is that the value of "initial branch" displayed in the UI is the branch that was most recently committed to, not the remote's default branch. I think this behaviour by EGit is incorrect.
What's the problem, you say? Why don't I change the initial branch drop-down box to "master", if that's what I want? Well, my problem is that I am using Buckminster to drive the checkout, and I never get to select the initial branch. Buckminster is just asking EGit (or maybe JGit) to clone the repository, but it's not getting back the correct result (default branch).
Is there a good reason for the existing behaviour, or should I file a bug? Any idea whether the fix is to EGit or JGit?
Powered by FUDForum
. Page generated in 0.01639 seconds