Is it safe to use git with multiple users when the central repository is on a windows file share?

We are a team of less than ten persons that need to quickly set up a git server that supports active directory based authentication.

The simplest solution seems to be to use a file share with a bare git repository and reaching it using a unc path, e.g.

  • GIT: How is safe concurrent push implemented?
  • How start identical jobs with different parameters in parallel execution?
  • When multiple clients push to same remote repository, how does git deal with concurrency issues?
  • Concurrency in a GIT repo on a network shared folder
  • Are concurrent git pushes always safe if the second push only has fast-forwards from the first push?
  • Are rugged Repository instances threadsafe?
  • git clone //server/share/repo.git
    

    However, we are a bit worried about robustness. Are there no issues with concurrency when several people use the same git repository and there is no actual server component running?

    Clients are running windows 7, server is Windows Server 2008R2. Using msysgit 1.8.1.2

    (I am well aware that there are many other git server solutions, but, especially given the requirement of AD authentication, they are not as simple to set up)

  • How to permanently add upstream location to git repo?
  • Bitbucket ssh public denied
  • Can Git be used as an approval system?
  • fatal: early EOF fatal: index-pack failed
  • Large file support: Normal files and git annex files in the same repo on windows? git add fails with fatal: This operation must be run in a work tree
  • How do you remove Microsoft Git Provider?
  • One Solution collect form web for “Is it safe to use git with multiple users when the central repository is on a windows file share?”

    It seems the only times the AR Auth will be in play is pushing/pulling.

    When you clone the git repo, the entire history will be cloned as well, so every user will have a complete repo.

    If the file share fails, any user can replace the code on a new share by pushing their code up.

    Concurrency is not an issue – since git is distributed it handles concurrency differently from other VCSs: no file locks, etc.

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