Git for windows constantly corrupting

I’m building an app using jQuery Mobile, PhoneGap, Exporting with Xcode and source control with GIT for windows.

I’m obviously doing something seriously wrong because after 5-10 commits the repository becomes corrupt and I can’t use it any more, this is the 5th or 6th time, my app is getting pretty advanced, and I have NO RECORD whatsoever of the changes made over time. In fact at this point source control for this app is a lost cause.

  • How To Stop Git-Bash command on windows
  • Adding plugins from specific revision Github project to the Cordova project
  • Cordova - Install AdMob Plugin on Android Failed (Mac)
  • Failed to get absolute path to installed module
  • angular 2/ionic2/cordova what to skip source control
  • best way of setting up a phonegap multiplatform project repository
  • The commits are not extraordinary, in fact I could change a line or two and it will work splendidly, the next line or two: Failed to Commit!

    Is anyone having this issue, have you figured out why?

    Actually trying a commit yields:

    commit failed – Failed to create a new commit

    git fsck yields:

    Checking object directories: 100% (256/256), done.
    broken link
    from tree ‘long alphanumeric’
    to tree ‘long alphanumeric’
    dangling blob ‘long alphanumeric’
    dangling tree ‘long alphanumeric’
    dangling blob
    ‘long alphanumeric’
    dangling blob ‘long alphanumeric’
    blob ‘long alphanumeric’
    dangling blob ‘long alphanumeric’
    missing tree ‘long alphanumeric’

    I have restarted my repo about a dozen times and this will happen half-way through the day every time…

  • Git - Ignore directories based on their contents
  • Git Svn Migration - Handling directory of binaries
  • SOA Webservices - How to manage individual service development on Git
  • Git pull doesn't know which branch to merge with
  • changing the git structure
  • GIT POST-MERGE Hook, Get updated files
  • 2 Solutions collect form web for “Git for windows constantly corrupting”

    • You have to test your repository with git fsck,
    • You can clone repo in some another location and try to work with clone
    • You can change Git-client (maybe it will help, but I doubt it)
    • You can send Git to trash and use another SCM

    Use GitExtensions – way better and functional!

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