What is the difference between “git init” and “git init –bare”?

by

Non-Bare Git Repo

This variant creates a repository with a working directory so you can actually work (git clone). After creating it you will see that the directory contains a .git folder where the history and all the git plumbing goes. You work at the level where the .git folder is.

Bare Git Repo

The other variant creates a repository without a working directory (git clone --bare). You don’t get a directory where you can work. Everything in the directory is now what was contained in the .git folder in the above case.

Why You Would Use One vs. the Other

The need for git repos without a working directory is the fact that you can push branches to it and it doesn’t manage what someone is working on. You still can push to a repository that’s not bare, but you will get rejected as you can potentially move a branch that someone is working on in that working directory.

So in a project with no working folder, you can only see the objects as git stores them. They are compressed and serialized and stored under the SHA1 (a hash) of their contents. In order to get an object in a bare repository, you need to git show and then specify the sha1 of the object you want to see. You won’t see a structure like what your project looks like.

Bare repositories are usually central repositories where everyone moves their work to. There is no need to manipulate the actual work. It’s a way to synchronize efforts between multiple people. You will not be able to directly see your project files.

You may not have the need for any bare repositories if you are the only one working on the project or you don’t want/need a “logically central” repository. One would prefer git pull from the other repositories in that case. This avoids the objections that git has when pushing to non-bare repositories.

Hope this helps

More Related Contents:

  1. Ignore files that have already been committed to a Git repository [duplicate]
  2. Git for beginners: The definitive practical guide
  3. Multiple GitHub accounts on the same computer?
  4. How to list branches that contain a given commit?
  5. Which commit has this blob?
  6. How can I delete all Git branches which have been merged?
  7. How can I make git accept a self signed certificate?
  8. What is a tracking branch?
  9. Git: “Corrupt loose object”
  10. Rebasing a branch including all its children
  11. What’s the best visual merge tool for Git? [closed]
  12. Preferred Github workflow for updating a pull request after code review
  13. git gc –aggressive vs git repack
  14. git push to multiple repositories simultaneously [duplicate]
  15. How do I change the author and committer name/email for multiple commits?
  16. How do I reset or revert a file to a specific revision?
  17. Git interoperability with a Mercurial Repository
  18. How to perform better document version control on Excel files and SQL schema files
  19. Locking binary files using git version control system
  20. Can I make a user-specific gitignore file?
  21. Git mergetool generates unwanted .orig files
  22. git commit frequency
  23. Git Diff of same files in two directories always result in “renamed”
  24. Git: How to reset a remote Git repository to remove all commits?
  25. How do I check out a specific version of a submodule using ‘git submodule’?
  26. Git: How to make outer repository and embedded repository work as common/standalone repository?
  27. Is there a way to compare two diffs or patches?
  28. How to perform a three-way diff in Git without merging?
  29. Clone only the .git directory of a git repo
  30. Other consequences of `git push –force`?

Leave a Comment