Gitkraken stuck at opening repo

Question

Every time I open gitkrarken it gets stuck at opening repo icon. I can\'t open/clone/init repo. I heard some others have the same problem but no one seems to know why this i

Answer 1

Deleting the index.lock in my Project/.git folder worked for me. Btw it's a hidden folder.

Answer 2

Not a proper solution, but I'm having the same problem. I've been able to work around it by closing down Visual Studio before opening GitKraken. It only gets stuck when opening and VS is already open.

Answer 3

I know this is an older thread but I had this issue today. It was caused by having a large number of files added to my repo without adding them to the .gitignore. I threw the COCO dataset into a deep learning repo so git was trying to list all 100k or so images, causing the crash. I just added the COCO directory to the .gitignore and everything went back to working like normal.

Answer 4

To me the problem was that the git database was not compacted. git gui showed that notification (enter link description here). By compacting it (through git gui or git gc, I assume) it fixed the problem with GitKraken.

Answer 5

I was helping a friend with the same issue. He was using gitkraken with IntelliJ on a windows 10 VM. The solution that worked for us was: *Deleting the hidden .git folder, in the folder where you have whatever program your working on (the reason why is because gitkraken is trying to open the repo which is why it keeps popping up with the error) Afterward gitkraken should not have the error anymore because you deleted the repo. Now just clone the repo from GitHub and just place the newly cloned repo in the same place the old repo was.* Side note: if you try to open the repo from the recent tab in the open repo you will more likely to get an error saying something about not finding it. (its because that's the old repo you deleted) you will have to browse and open the newly cloned repo manually in order to make it work.

Answer 6

In my case, the issue was with a .jfm (binary) file that my SSDT (Sql Server Data Tools) project generates. When that file changes, GK starts having this issue. If I manually commit (or revert) that file, the problem goes away.