Should I store git repository in Home or Eclipse Workspace?

I’m just moving from svn to git, and am keen to lay some good foundations.

By default Eclipse wants to store my local clone repository in ~/git. I’m more comfortable keeping all data for a task in the same workspace – so I’m inclined to keep it in my workspace.

Are there any significant pros/cons I should consider?

I don’t intend doing a lot of branching – I’m really going down the dvcs route mostly to overcome some unreliable internet comms issues.

  • Empty tag list for existing repository with JGit
  • Upload maven pom.xml to Git repository?
  • maven-release-plugin deploying SNAPSHOT
  • Creating a Clone Custome object
  • Commit with specific date using JGit Eclipse
  • Lego Mindstorms ev3 leJOS finding libraries during compilation
  • Netbeans Maven project from cloned GitHub Java (with jni and C) repository
  • chromedriver fails on windows jenkins slave running in foreground
  • 3 Solutions collect form web for “Should I store git repository in Home or Eclipse Workspace?”

    I’m too switching to Git in Eclipse, and reading about this issue. It seems that current wisdom (though not everyone agrees) is:

    • Get used to NOT having your projects below the workspace directory.

    • Have one git repository for each group of related eclipse projects (and perhaps more files, of course). The concept of “related projects” is up to your convenience [*]

    • For each repository, one first level directory for each Java project. This implies that you’ll have a .git/ directory, and, at the same level, the project directories.

    Example: suppose that, “before GIT”, you had one eclipse workspace with several projects:

    /wk/workspace/projXXXtest/  (related with the previous)
    /wk/workspace/projYYY1/     |
    /wk/workspace/projYYY2/      >  three related projects
    /wk/workspace/projYYY3/     |
    /wk/workspace/projZ/        (a project you are not going to version in git)

    Then you’ll create two empty directories, one for each repository, say:


    and afterwards, with the new GIT layout, you’ll have:

    ~/repositories/XXX/.git/   (XXX related repository - non-bare)
    ~/repositories/YYY/.git/   (YYY related repository - non-bare)

    Eclipse (EGit) does all this for you when you click Team->Share over an existing project and specify (in the example) ~/repositories/XXX/.git/ as repository, (~/repositories/XXX/ as “Working directory”, leave “Path within repository” blank).

    [*] Bear in mind that here each group of projects is, from the Git point-of-view, just a set of directories inside a repository. Some relevant implications: in the above example, you’ll never have in the Eclipse workspace two different branches/versions of projects projYYY1projYYY2 simultaneously; and, say, when you tag a project commit, you are actually tagging the full repository (group of projects) commit.

    The .git should be where your working tree is (that is the files representing the current HEAD of the current branch you are working on)

    Remember that with Git, branches are not directories (as opposed to SVN), so your working tree will represent directly a branch content, not several directories (for your various branches), followed by a content per branch.

    I usually like to keep my project sources separate from my Eclipse workspace, but that is a matter of preference.

    I think, it is a good idea storing the git version tree outside the workspace. This way it is possible to separate projects from different repositories, but still handle them in the same workspace.

    Additionally, if you put the code outside the workspace, you can organize your projects hierarchically outside the workspace (in the working copy), but still see the flat representation in Eclipse.

    Git Baby is a git and github fan, let's start git clone.