gitkraken could not find a compatible repository

Well, I guess that there is an even more extreme step, in that you could delete the repo and re-clone but you would lose all local branches, stashes, and unpushed commits. Ok, if you are still having trouble and are CERTAIN that you do not need anything in your reflog, INCLUDING YOUR STASH, you can expire all of it now and clean up (garbage collect) the dangling refs: git reflog expire -expire=now -all The links can be found in GitKraken Client’s context menus under Copy link to remote/commit. When specifying a branch, the latest commit of that branch will be focused. The links will focus GitKraken Client on the commit, branch, or tag specified. To get my GitKraken working again, I need to go with the Nuclear Option. When shared, these links will both open and focus GitKraken Client to the linked repository. Do you want to create a new repository there', then I am provided with two buttons Initialize and Cancel. Those are temp files that should have been filled with data or deleted but were not, for. GitKraken: Repo opens, but says 'could not find a compatible repository' Hi All, Basically when I open my repository, sometimes it would display the error 'Could not find a compatible repository at 'pathname'. I also found some zero byte objects, which should not be. The corrupted lines in my log had loads of strange symbols and were like 4 time the length of the other lines. All of the lines should look very much the same (from-hash, to-hash, timestamp, user, message, and so on). git/logs/refs/remotes/*/* for any lines that look extremely unusual. A Solutionĭigging a little deeper I found that, apparently, something got corrupted in my reflog.

Other tools (Giggle, gitg, git-gui, and the git CLI) all seemed to work just fine.

However, after about a minute, it would unload the repo and start trying to load it again, but just hang trying to load. It would keep presenting this 'compatible repository' message even though it would load the repo and let me stage and browse commits. I just had this same issue with GitKraken.

Gitkraken could not find a compatible repository