gitkraken could not find a compatible repository

Gitkraken could not find a compatible repository update#

Read the docs and use GitHub Issues for support & feedback. v1.2.3) are released on the 'Stable' channel, while builds tagged with a b (e.g. b1234) are only released on the 'Continuous' channel.

Gitkraken could not find a compatible repository update#

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. Could not find a compatible repository gitkraken update You can change the update channel used by GitUp in the app preferences. 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 To get my GitKraken working again, I need to go with the Nuclear Option. Those are temp files that should have been filled with data or deleted but were not, for. This is particularly useful if trying to commit your hooks to the repository (e.g. I also found some zero byte objects, which should not be. 108 votes Upvote The core.hooksPath config allows you to set a directory where the hooks are located for a repository. The corrupted lines in my log had loads of strange symbols and were like 4 time the length of the other lines. Do you want to create a new repository there', then I am provided with two buttons Initialize and Cancel. All of the lines should look very much the same (from-hash, to-hash, timestamp, user, message, and so on). 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'. 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.