Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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
Community showcase
Published in Confluence

⚡️NEW Group for Confluence Cloud Admins

Calling all Confluence Cloud Admins!  We created a new Community Group to support your unique needs as Confluence admins. This is a group where you can ask questions, access resou...

107 views 2 9
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you