Github windows: Commit failed: Failed to create a new commit

Github

Github Problem Overview


I have: http://windows.github.com/

My current project has around 20k files, around 150MB (and not speaking about how slow it is and I cannot do a thing now) it doesn't even let me commit! I get this error: Commit failed: Failed to create a new commit.

That seems that nobody is having.

I've already deleted the folder and cloned again, no escape. What to do?

If I choose to open shell, all this *** crashes!


Edit:

Since the problem I've switched to Git Extensions and I didn't look back!

thanks for your answers

Github Solutions


Solution 1 - Github

This happened to me. Try opening up PowerShell and manually committing each file using the "git add [file name]" command. To see which files have been added, enter "git status" into the command line. The green files have been added, the red ones have not been added.

Once you've added them all, type "git commit." Then go back to Github for Windows and sync it up.

I'm not sure what causes this issue, but once I followed the above steps, Github went back to its normal, awesome behavior.

Solution 2 - Github

I had this problem too after an unexpected crash. I couldn't fix using the 'Open Shell' option as suggested. I had to open the Windows CLI (Start -> run -> cmd) and delete the index.lock file in my GitHub folder:

cd \Users\myUser\my\local\github\repo
cd .git
del index.lock

Then when I went back to the GitHub app, it committed successfully.


Note that for some people, according to comments, the file to delete doesn't have the .lock extension, so the delete command could also be del index.

Solution 3 - Github

Im using Githug for Windows (7) and faced the same problem. While using PowerShell I realized that I didn't fill Full Name and email address in tools > options. Look like a beginner mistake (and I am!).

hope it helps!

Solution 4 - Github

just try to commit a few from your updates. 5 for example. and then make another commit with all other updates.

Solution 5 - Github

I am using windows client and getting the same error. Then suddenly I realized that my local db in app_data was opened on the SQL management. It just simply can't commit the some files to github if they are opened or using at the other programs.

Just disconnected management studio closed it and just simply committed.
This may be your case also. Check your files out!

Solution 6 - Github

So guys this is the full steps I had to take in order to fix the problem...

  1. Using Process Explorer (you can download it form here http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx) I searched for any process referencing ".git\index" and then I killed it.

2)Then using Git Shell (Windows Power Shell) I went into the repository which was giving me such difficulty and then furthermore went into its .git folder. (cd .\your_respository_name\.git). I then removed the index.lock file in that directory (rm -r index.lock).

3)Then from within that same directory I ran git reset HEAD.

4)Then I manually committed each file using the "git add [file_name]" comand. (You can check that they were added successfully if when you run git status, the files are green.

5)Next run git commit if your files are added correctly.

6)Finally go back to github for windows and sync everything up and it should hopefully work and resolve the problem.

Solution 7 - Github

This issue seems to be a bug in the github client - I get it "all the time" on the machine on which i only installed the github client. I Never saw it on the git + github PC (I have not used it for a few days now). Doing the "git add ." and then "git commit" worked for me also on the shell - but that is the thing the GUI should be doing not me - otherwise I can just stick to the git shell client.

Solution 8 - Github

Had the same problem, couldn't commit or sync using the windows GUI, but I could commit the changes through the shell. Once I'd added the changes through the shell the windows GUI started to sync normally. Hopefully it's a one off.

Solution 9 - Github

I had an interesting issue - even though I had an excel file open called "Combined - ForImportv4.xlsm", Git UI had no problem checking that in but it gave the error in the OP's subject for the backup file "~$Combined - ForImportv4.xlsm" so I discarded that change and all went through.

PS: As for why i'm checking an Excel file into Git ... just don't got there :)...

Solution 10 - Github

I had this issue with the git windows desktop commit tool. I was getting this often and I figured out that Visual Studios was locking the files. To get around this issue I simply closed visual studio and the commit / sync worked fine.

Solution 11 - Github

I googled failed to create repository and ended up here.

My problem was that the description for my new repo was too long. There is a charlimit for the description, but GitHub tried to push it anyway and failed.

Solution 12 - Github

I just had the same problem, tried some of the suggestions on this post but none worked so what i did was, on the GiTHub client i went to tools -> settings and then click on the section where it says add/create default ignored files. Then hit Update and try to commit again through the client.

Solution 13 - Github

It happend to me when my project was opened in an IDE (Netbeans in my case), make sure non of the files you're about to commit isn't open in some program.

Solution 14 - Github

I checked the log file at C:\Users{user}\AppData\Local\GitHub\TheLog.txt and found this error:

LibGit2Sharp.LibGit2SharpException:

Could not open 'SomePath\SomeProject.opensdf':
 
The process cannot access the file because it is being used by another process.

I closed Visual Studio and the commit was then created successfully. n.b. I removed actual file path in the above error.

Solution 15 - Github

If you are new user make sure that you have confirmed your e-mail. Had same problem and confirmation fixed it!

Solution 16 - Github

You can manually navigate to index.lock which is found inside the hidden .git folder of your repository location. Once you delete index.lock you will be able to commit as per usual.

The easiest way to navigate to the folder will be to click on the folder breadcrumbs inside windows explorer and add \.git and press enter.

Solution 17 - Github

Just delete 'index.lock' in the '/.git/' directory. Solved the problem for me instantly.

Solution 18 - Github

I had this happen to me and this is the easiest way to fix it:

  1. Make a copy of your local folder that has the repo and remove the .git folder form it.
  2. Delete the original repo folder with files.
  3. Re-clone the repo from GitHub with the Windows client.
  4. Delete all of the files that get cloned except for the .git folder.
  5. Copy all files from the copied folder into the new clone folder.

Add in your commit notes and the commit should work this time.

Solution 19 - Github

I had the same problem and I fixed it by renaming one of the file because its name was too long. This fixed the problem. Here is error message from git shell:

fatal: unable to stat 'plugins/com.napolitano.cordova.plugin.intent/example/app/platforms/android/CordovaLib/build/intermediates/classes/debug/org/apache/cordova/NativeToJsMessageQueue$OnlineEventsBridgeMode$OnlineEventsBridgeModeDelegate.class': Filename too long

Solution 20 - Github

I REBOOTED my Windows 7 machine and tried again - IT WORKED!

I had the "Commit failed: Failed to create a new commit" and tried to delete the index or index.lock file via windows command prompt and that didn't work. I deleted it via windows explorer, that didn't work.

I tried to check credentials like another reply in this list said, but couldn't figure it out and the credentials seemed 'ok.' So - I rebooted. Viola.

I'm not sure this will help anyone, I'm not all that great w/ this stuff, but trying.

Solution 21 - Github

I deleted ".git" in children directory and the problem was resolved.

Solution 22 - Github

It happened to me once ,I had a empty repository inside of the repository that I cloned. It was a silly mistake though but could happen .

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionTotty.jsView Question on Stackoverflow
Solution 1 - GithubmpoulshockView Answer on Stackoverflow
Solution 2 - GithubunderblobView Answer on Stackoverflow
Solution 3 - GithubDaniel VitorView Answer on Stackoverflow
Solution 4 - GithubSorokin AndreyView Answer on Stackoverflow
Solution 5 - GithubosmancelikView Answer on Stackoverflow
Solution 6 - GithubSabashan RagavanView Answer on Stackoverflow
Solution 7 - GithubMarcView Answer on Stackoverflow
Solution 8 - GithubScarelView Answer on Stackoverflow
Solution 9 - GithubnchaudView Answer on Stackoverflow
Solution 10 - Githubuser1593329View Answer on Stackoverflow
Solution 11 - GithubNavinView Answer on Stackoverflow
Solution 12 - GithubKomengemView Answer on Stackoverflow
Solution 13 - Githuberic.itzhakView Answer on Stackoverflow
Solution 14 - Githubcracked_machineView Answer on Stackoverflow
Solution 15 - GithubMaciek NalewczyńskiView Answer on Stackoverflow
Solution 16 - GithubSam KeightleyView Answer on Stackoverflow
Solution 17 - GithubDualCoreView Answer on Stackoverflow
Solution 18 - GithubJason RundellView Answer on Stackoverflow
Solution 19 - GithubStrabekView Answer on Stackoverflow
Solution 20 - GithubFloppyDiskView Answer on Stackoverflow
Solution 21 - Github Юрий СветловView Answer on Stackoverflow
Solution 22 - GithubSameera De SilvaView Answer on Stackoverflow