concept of bare shared repository in git

I have been facing difficulty in understanding the bare repository . I have read everywhere that a shared repo is a bare repo. Why must it be a bare repo? Can’t it be a normal repo which collaborators clone and then push/pull?

  • How to set Araxis as diff / merge tool for MSYS git?
  • How do I merge a binary file?
  • OpenCV 3.0.0 make error with FFMPEG
  • Bash shell script error sh: '
  • Does GIT supports mirroring or proxy concept?
  • Reverting a series of pushed merges and commits in Git (without rewriting history)
  • How do i move my current work to a topic branch?
  • Force git custom merge driver for the purpose of merging pom.xml (maven) files
  • Untrack all files on git
  • Undoing a git rebase
  • Use custom NuGet feed in Visual Studio Online
  • How can I remove my last commit in my local git repository
  • One Solution collect form web for “concept of bare shared repository in git”

    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.

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