Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,367,825
Community Members
 
Community Events
168
Community Groups

Change default branch in git for fisheye-hosted repos?

If I'm hosting my own bare git repo, I can go into it and run the following command to make the 'develop' branch get checked out by default when cloning:

$ git symbolic-ref HEAD refs/heads/develop

Unfortunately, when I go into the fisheye bare repo (I'm running it on Linux) and do the same thing, 'master' still gets checked out by default when I clone. I've also tried the various types of re-indexing after doing so, but it doesn't work.

I actually got this to work once briefly, but I was so frustrated at that point that I don't really know which steps caused this to happen, and I can't reproduce it.

I've also tried 'git remote set-head origin develop' from the client and then pushing, but that doesn't seem to help. It's one of the things I did the time that it worked, though.

I'm running Fisheye 2.7.8, and I'm using a repo I created myself (carefully converting from subversion) and am pushing (with --mirror) up to a bare Fisheye-managed repo.

2 answers

1 accepted

0 votes
Answer accepted
Conor Atlassian Team Mar 22, 2012

This is not currently possible through the FishEye UI. You can go directly to the bare git repo that is managed by FishEye if you have access to the FishEye server and use git symbolic-ref as you have described. Any clones done after that will default to the develop branch.

I never got that to work, but we're using Stash now, anyway

Alternately, a way to make managedUrl_tag.class display "git clone -b develop https://user@server/git/repo.git" as the "Clone this repository" string could be an interesting workaround. But that's nowhere near what I'm actually looking for.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events