Ok, part of entering the blogoshere was that it would become my penance for lurking on the hundreds of other blogs and online resources that helped me solved countless errors and programming time sinks. I was rather enjoying my day off until I decided to be productive and see if I could identify why this error popped up when I was on a client site this week.
Create a tree? That's easy ..
Just to prove I broke Google:
Thanks Google, for nothing ...
I still haven’t got to the root of the issue, but my development environment is on a Mac, Snow Leopard 10.6.6, and GitX 0.7.1.
The work around was to clone the remote repository on Github again locally, or to simply copy and paste the working directory in finder. The duplicate directory doesn’t encounter this error on commit.
Hopefully someone will find this and it will save them some time down the road … If I can help but one lost programming soul a couple of hours, then all this blogging fuss would have been worth it.
rado
Thanks for sharing. We also encountered this error with gitx.
anonymous
I think this error is related to files that were stashed before. Try looking at each file and see if they appear both on staged files column and unstaged, then remove from staged, add it again to staged and try to commit.
It worked for me.
Raf
I had this error when trying to commit a bunch of code, while having new files in my working directory (white ones in the left “Unstaged changes”)
They were generated files so i didn’t really need them, and after deleting them, i was able to commit again using GitX.
I don’t know exactly to what this is related, but thanks for sharing your experience, hopefully mine will help somebody out there.
Titus Says :
I had this same issue and it was because I didn’t setup my email and name with `git config`.