Flare 2019 - destination already in use by another project

This forum is for all Flare issues related to using Source Control.

Flare 2019 - destination already in use by another project

Postby Flareon on Fri Jan 22, 2021 9:26 am

I'm trying to bind an existing local project to Bitbucket using the Bind project feature in the Flare UI and when it attempts to push to the new repo I've created it says "destination already in use by another project". I've come across this problem a few times over the years and each time, the previous resolution doesn't seem to fix the current problem.

Environment:
Madcap Flare 2019
Windows 10 laptop
Bitbucket.org/mycompany name/

I thought my local folder structure might be a problem as one of the folders already binds to another repo in bitbucket.
Parent Folder - Not bound to source control
Child-folder1 - bound to a Bitbucket repo
Child-folder2 - trying to bind to a brand new repo called home_page which I created about 5 minutes ago.

The home_page repo contains only a .gitignore file.

Has anyone managed to successfully bind a project straight off the bat using the Bind project feature in the Flare UI?

Things I've tried:
1. Checked that there wasn't a .readme file in the repo.
2. Followed the Madcap Help 2019 instructions called 'Binding a project to Git' - https://help.madcapsoftware.com/flare20 ... ol-git.htm
3. Being logged into Bitbucket whilst trying to Bind and not being logged into Bitbucket when trying to bind.
4. Using https://username@bitbucket.org/companyn ... e_page.git as the repo folder to bind to.
5. Using https://bitbucket.org/companyname/home_page.git as the repo folder to bind to.

I fear this is going to take me hours to figure out. Short of calling Flare Support, does anyone have any other ideas I can try? Anything much appreciated!
Last edited by Flareon on Mon Jan 25, 2021 3:50 am, edited 2 times in total.
Flareon
Jr. Propeller Head
 
Posts: 8
Joined: Fri Aug 02, 2019 3:18 am

Re: Flare 2019 - destination already in use by another proje

Postby Flareon on Fri Jan 22, 2021 10:00 am

I've now also tried moving my child folder 2 out of this folder structure and attempting to bind to the same repo. However, get the same error.
Flareon
Jr. Propeller Head
 
Posts: 8
Joined: Fri Aug 02, 2019 3:18 am


Return to Source Control

Who is online

Users browsing this forum: No registered users and 1 guest