Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

New repository turns into remote branch in current repo

Atle Hansson September 27, 2017

Hi all, I created a new repo in Bitbucket and I thought I connected it correctly to SourceTree as usual, cloned it from the repository browser, etc. But it now both shows up as a remote branch inside of the repository I already had from before AND as its own repository in the repo browser. This is how it looks in old repo: https://imgur.com/a/ac6zz

Commits to the new repo (dev-tools) list correctly in the history for that repo, but simultaneously shows up in the other repo as shown in the screenshot.

I have deleted the unwanted remote from the old repo, the mess is cleaned up, but I'd like to know what I did wrong when I cloned the remote repo in order to avoid problems in the future. Here is what the config file looked like before I deleted the dev-tools remote:

 

[core]
repositoryformatversion = 0
filemode = true
bare = false
logallrefupdates = true
ignorecase = true
precomposeunicode = true
[remote "origin"]
url = https://[...redacted]@bitbucket.org/redacted/wp-themes.git
fetch = +refs/heads/*:refs/remotes/origin/*
[branch "master"]
remote = origin
merge = refs/heads/master
[remote "dev-tools"]
url = https://[...redacted]@bitbucket.org/redacted/dev-tools.git
fetch = +refs/heads/*:refs/remotes/dev-tools/*
  

Tips?

1 answer

0 votes
minnsey
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
October 2, 2017

Hi
We've not seen that before and we'd need to try and re-produce the problem.

Just to clarify:

You had repository A open in Sourcetree?
You created a new repository B in Bitbucket?
You used the 'Clone in Sourcetree' option in Bitbucket?
This opened the Clone panel in the New tab in Sourcetree?
You selected a path and a folder to clone into and cloned?

You then found repository B listed under the local repositories in the New tab, and open in its own tab AND found the remote for repository B had been added to repository A ?

Is that correct?

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events