concept of bare shared repository in git

by

It needs to be a bare repo because a not bare repo would have a working tree (meaning a specific version of that repo checked out and with files visible).

Each time you are pushing to a non-bare repo, you have no guarantee that its working tree will reflect what you are pushing, since by default said working tree will be untouched.
(Imagine if a push would trigger an update of the working tree: the files would change all of a sudden without any control from users on the receiving end)

That is why it is simpler to have a bare repo as an upstream repo (one you push to): no working tree to manage/update.

See more at “all about “bare” repos — what, why, and how to fix a non-bare push“.

It doesn’t have a checked out tree, so it just does what the “server” notionally does in a centralised VCS — records commits, branches, etc when you push to it, and gives you the latest versions when you clone or pull from it.

More Related Contents:

  1. What’s the -practical- difference between a Bare and non-Bare repository?
  2. Writing a git post-receive hook to deal with a specific branch
  3. How do I push a new local branch to a remote Git repository and track it too?
  4. How do I update or sync a forked repository on GitHub?
  5. Remove a file from a Git repository without deleting it from the local filesystem
  6. How do you merge two Git repositories?
  7. Download a single folder or directory from a GitHub repo
  8. How to move some files from one git repo to another (not a clone), preserving history
  9. How to convert a normal Git repository to a bare one?
  10. How to count total lines changed by a specific author in a Git repository?
  11. How do I rename both a Git local and remote branch name?
  12. Moving Git repository content to another repository preserving history
  13. Repack of Git repository fails
  14. Git – Ignore files during merge
  15. Untrack files from git temporarily
  16. How do I clone a Git repository into a specific folder?
  17. heroku: src refspec master does not match any
  18. Split large Git repository into many smaller ones
  19. Is it possible to pull from one repo and push to other one?
  20. Moving a git repository up one hierarchy level
  21. How do I rename a repository on GitHub?
  22. Delete local Git branches after deleting them on the remote repo
  23. Create a GitHub repository from command line
  24. How do I convert a bare git repository into a normal one (in-place)?
  25. GitHub changes repository to the wrong language
  26. “fetch –all” in a git bare repository doesn’t synchronize local branches to the remote ones
  27. Git: add vs push vs commit
  28. Linking a single file from another git repository
  29. git push to remote repository “Could not read from remote repository”
  30. git subtree: possible to change subtree branch/path in a forked repository?

Leave a Comment