How to create a GIT repository in existing folder full of files?

Hello, I believe this may be considered as a stupid question but I didn't find the answer. I'm brand new to GIT and SourceTree and I want to create a GIT repository in existing folder which contains my project files.

I know how to create a GIT repository in empty folder but I don't know how to create GIT repository when there are already created files.

 

Sorry for my English errors,

Defozo

9 answers

1 accepted

This widget could not be displayed.

The safest way to do this is to create a new repo on the server, clone the empty repo into a new folder and copy/move the existing files into that.

 

So it can't be done the other way? It smells to me like a lack of functionality. Anyway, thanks for the answer.

You can also do a git init in the existing folder: http://git-scm.com/docs/git-init and then set a remote and push it to the server. Since the remote repo has to exist when you push your changes, I think the above method is more straightforward / less error-prone.

It certainly can be done the other way, as Balazs mentioned, but it becomes more complex if you are trying to push to a remote. You can create the new repository in the populated folder exactly the same as if the folder were empty. Once the repo is created, you'll need to add and commit the existing files.

This widget could not be displayed.

This seems to me to be a very common scenario for individual and small teams and should be supported, especially when one is using Sourcetree with Bitbucket. An experimental project is deemed interesting enough to save, so one should be able to (with minimal effort) create an empty remote repo and push the local code to it as the first checkin without the hassle outlined above.

Balazs shared a hassle-free method in his comment, with the warning that there is increased risk of mistakes. Specifically that risk is, if you set a remote without checking out from it, there's a chance you'll overwrite something if the remote isn't actually empty (maybe a typo caused you to add the wrong remote).

It's not really hassle-free if it involves dropping to the command-line to do it. It also still looks like a multi-stage process (init local repo, create remote repo, set remote) when it ideally should be a single-step process from the SourceTree GUI. Shouldn't the process of securing one's source code have a low a barrier to entry as possible?

SourceTree isn't an software interface for BitBucket. Git is a decentralized VCS, which means that having a remote is not automatic. Since it's not automatic, it requires additional steps to set up. Also, you can do this in SourceTree. Use the third tab in the "Add Repository" dialog and choose the existing folder as the destination.

I mentioned BitBucket only in the context that if doing this required communication outside standard Git or Mercurial, then Atlassian's ownership of both SourceTree and BitBucket could be leveraged to accommodate this on a technical level. Since it can be accomplished (just crudely) it's a moot point. I did just try this (for both Git and Mercurial) and the following steps do work to achieve the OP's goal without relying on the kludge clone & copy approach. 1) Create new repo (third tab) to create local repo 2) Create new empty repo on server (I was only able to do this from the "clone repo" tab then cancelling the clone operation after viewing my Bitbucket Repos and creating a new repo there) 3) Add remote (required I again open the clone dialog to get the proper URL) This is still kludgey for several reasons: * create remote repo step is (can only be?) done as a side effect of cancelling a clone operation. * In documentation I've looked at, creating a local repo is described for creating a repo that will not have a remote, so it is not clear that this step will lead towards the solution * similarly, adding a remote is described as a way to take a repo that has been cloned and then moved to re-sync with an existing remote, and not as a part of creating a remote repo for an existing bit of code. * the FAQs for Sourcetree do not mention this use case, (the FAQs are slim overall) Since this procedure is, in my experience, how the vast majority of new (as opposed to forked) repos are made (from an existing project not in source control on a local disk) it really should be easily and clearly supported (as a valid feature request) in SourceTree.

That's a fair argument. Feature requests can be made at jira.atlassian.com. I recommend posting a link to your FR here (as an answer) to help like-minded individuals find it and vote it up.

This widget could not be displayed.

Feature request here https://jira.atlassian.com/browse/SRCTREEWIN-3126

I made it for the Windows version – not sure if it is appropriate to make a duplicate for the Mac version, or if there is a better way to specify platform-independent features.

wow! This is how feature requests are treated, apparently they get closed with: "This issue affects a version we no longer support...." which somewhat flies in the face of this porttion the mssion statement "SourceTree simplifies how you interact with your Git repositories so you can focus on coding."

:(

This widget could not be displayed.

Here is the easiest way to do this:

 

Sourcetree comes with git. 

1) Add the path to GIT to you environmental path variable so git.exe can be found. 

( Windows example: c:\Users\UserName\AppData\Local\Atlassian\SourceTree\git_local\cmd\)

2) Open the windows cmd line and navigate to the directory you want under source control

(after adding the path if you have the cmd line open you must close and open it to refresh it)

3) type git init and press enter. 

4) Now the repository is a GIT Repo!  yea!

5) In SourceTree goto "Add a repository"

6) Browse to your repository

7) The repo should be a Git Repo!  Yea!

9) Press "Add"  and your done.  

 

The whole trick is to initialize the repo using Git and you don't need SourceTree for that.  

Does not compute: 

"Simple for beginners

Say goodbye to the command line - simplify distributed version control with a Git client and quickly bring everyone up to speed."

ref: https://www.sourcetreeapp.com/

This widget could not be displayed.

 

Here's how I do it:

Create new Bitbucket private repository online in your account

Select "have existing project" option

In command line (CL) navigate to project folder and type

git init
git add .
git commit -m “your description”.

 Copy and paste code provided by BitBucket for “git remote…” in CL at project root

Copy and paste code provided by BitBucket for “git push…” in CL at project root
Enter password if asked

Check everything uploaded using SOURCE menu option in Bitbucket

Use clone option in Sourcetree to clone project to a new folder

For me, all that's now needed is to copy the source .ENV file to the new clone and it should work fine. Thereafter Bitbucket/GIT/Sourcetree should track and maintain your project.

This widget could not be displayed.

i guess you can 1. create a new project in empty folder, 2. move the .git to your existing project, 3. open the existing project in Sourcetree.

creating repository in existing folder is something like headphone jack for iphone, or food in communism country. They insist that you don't need it but you are needing it.

This widget could not be displayed.

Nice .... giving up before I even start with this product...will stick with VS plugin arg....

This widget could not be displayed.

When you create a new repo you will be greeted with this:

Get started with command line

 I have an existing project

  1. Step 1: Switch to your repository's directory

    cd /path/to/your/repo
  2. Step 2: Connect your existing repository to Bitbucket

    git remote add origin https://username@bitbucket.org/username/reponame.git

    git push -u origin master

To me, the point of this request is a way to do it without having to go to the command-line. If you have to go to the command-line all the time, why use a GUI? Without getting into the larger arguments, this seems to me to be one of the fundamental and fatal flaws of nearly all *nix based tools, is their ultimate reliance on having to use a command-line tool to do anything beyond trivial work.

This widget could not be displayed.

Can't believe this feature has been requested 3 years ago and it's still not a thing. Yes, you can do it in git, but the whole point of using SourceTree is removing the need to go to terminal. For more advanced features I understand the need of git, but this request seems common and basic enough.

Suggest an answer

Log in or Sign up to answer
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Published May 30, 2018 in Sourcetree

Tip from the team: configuring Git or Mercurial in Sourcetree

Supported Platforms macOS Windows To make using Sourcetree as simple yet powerful as possible we embed (bundle) dependencies such as Git, Git LFS, and Mercurial. We strive to keep these...

711 views 1 3
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you