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

I just had the same problem. I found that my .git/logs/HEAD had a bad entry (don't know how that happened nor why gitg and the git CLI both ignored the issue). Totally a problem with my repo, not GitKraken.

More detail...

To figure this out, I cloned the repo into a separate directory and meld'd them to see what was different. I opened GitKraken to this new clone; all's well. I then started copying things over from the old repo directory to the new one (objects, refs, logs, etc.). Once I copied that log file over, GitKraken went back to the "Opening repo" message.

Digging deeper into that log file I found a bad line. I was able to determine from the context how to re-create that bad line. Once I fixed it, GitKraken was happy.

Answer 2

In my case, such GitKraken glitch is reproducing stably, when I make an attempt to attach some Dokku (https://github.com/dokku/dokku) remote repository with git remote add. Removing it fixes the issue. I think Heroku repos may cause the same issue, though never checked it.

UPD: It is not Dokku/Heroku which causing troubles in my case. Any time when I use SSH-like URL for any remote repository (like git@github.com:reponame...), I get cyclic reloading of GitKraken. By coincidence, Dokku and Heroku use SSH-like URLs by default. Once SSH-like URLs are removed or changed to HTTPS, GitKraken is ok.

Answer 3

By now, I'm sure this answer won't help who asked the question, but maybe this will help people in the future. I just simply deleted and re-cloned the repo that GitKraken was trying to open. Worked like a charm for me.

Answer 4

If it's only one specific repo, make sure you don't have huge files in your repo. Adding them (or the respective folder) to the .gitignore should resolve the issue.

Answer 5

Currently for a workaround I do View->Reload (Ctrl + R).

Answer 6

just had a similar problem with a spring-boot(mvc) project w/ embedded H2 db, on GitKraken(2.7.1)

Turns out when the app is running, it will cause this problem on selective hardware that use that repo, So make sure your repo isn't being actively used while sync-ing