Master failed to write error while pushing commit

I have a git repository on a company network drive and had no problem pulling from it. However, i wasn’t able to push any commits into it, though I had a few good luck but recently I couldn’t get anything in it. The error was:

C:\Program Files\Git\bin\git.exe push “origin” master:master error:
Couldn’t set refs/heads/master To //software/pdd.git/ ! [remote
rejected] master -> master (failed to write) error: failed to push
some refs to ‘//software/pdd.git/’ Done

  • How to move manually versioned files to git (version control)?
  • Git: How do I merge complex branches that have widely diverged with some missing history?
  • Git: Zombie submodule
  • Save GIT Credentials using Git Credential Manager for Windows - Not working
  • python import from sub-directory in a git safe way
  • git lost my edit history without merge and conflict
  • I suspect that it got to with the master file. On Windows, it shows that I might have been put into a network group that does not allow me to do modify but was able to read, write and execute.

    My question is: If i was able to push a few times before, this file permission thing shouldm’t be a hassle to me. If it, indeed, that I don’t have enough privillage to modify, is there a workaround?

    PS: The company is reluctant to change my network group to another, which would enable me to modify files.

  • Migrating a multi-project Subversion repo with a common trunk to Git?
  • JGit: Transport Exception - reject HostKey: bitbucket.org
  • Listing all repositories served by git-daemon
  • Map remote repository to an existing directory with files
  • Git / Gitolite Some folders empty, permissions issue?
  • How can I get git and copSSH to look in the correct directory for keys?
  • One Solution collect form web for “Master failed to write error while pushing commit”

    Check the question “Pushing to a Git repository on an NFS share fails”:

    The NAS is doing weird things to permissions, setting the sticky bit on all directories. This explains the behavior. An additional chmod solved the problem.

    That means this is a permission issue on the target (remote) side, as illustrated in “Git issues after upgrading to osx Lion”:

    there was an odd permission for everyone as ‘custom’. I updated this to be ‘Read & Write’ and the commit was finally successful.

    As a “workaound”, See this Error section:

    I just deleted my bare repository and created a brand new one and pushed my changes over there. And everything works again.

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