What’s the -practical- difference between a Bare and non-Bare repository?

I’ve been reading about the bare and non-bare / default repositories in Git. I haven’t been able to understand quite well (theoretically) the differences between them, and why I should “push” to a bare repository. Here’s the deal:

Currently, I’m the only one working on a project on 3 different computers, but there will be more people involved in it later, so I’m using Git for the version control. I clone the bare repo on all computers, and when I finish my modifications on one of them, I commit and push the changes to the bare repo. From what I’ve read, the bare repository does NOT have a “working tree”, so if I clone the bare repo, I won’t have a “working tree”.

I’m guessing that the working tree stores the commit information, branches, etc. from the project. That wouldn’t appear in the bare repo. So it seems better for me to “push” the commits to the repo with the working tree.

Then, why should I use the bare repository and why not? What’s the practical difference? That would not be beneficial to more people working on a project, I suppose.

What are your methods for this kind of work? Suggestions?

11 Answers
11

Leave a Comment