Gitkraken doesn't show branches and commits

Question

When I try to open a repository in a xampp server with Gitkraken I can\'t view branches or commits, just the message \"Displaying 2000 commits. Adjust this setting in Preference

Answer 1

I deleted my repository and installed again. The error is gone.

Answer 2

I had the same problem, unfortunately Yaspers answer did not work for me since I did not make a shallow copy.

Turns out my GIT repository was corrupted for whatever reason. After opening the command line and executing git fsck, I got this error message:

error: packfile [some hash].pack claims to have 811 objects while index indicates 874 objects

I tried to reset the changes: git reset --hard. It sort of worked (be aware that this deletes all of your uncommitted changes!). Git Kraken was able to display new changes but still was not able to display the whole tree.

In the end, the only thing that worked for me:

• cloning the repository into a new location
• copying all files, that were not tracked by GIT (files that I only needed on my local PC, for example, some .env files) to the new location

It is not the solution I hoped for but at least I did not lose the whole repository.

Answer 3

Ran into this because I had to check out my repo with limited depth. Cloning the repo fully ran into a closed connection, so I checked out a shallow copy:

git clone http://github.com/large-repository --depth 1

But this resulted in GitKraken omitting the history like what you ran into. GitKraken didn't handle the depth nicely; in order to fix it, I had to run this after the initial clone:

git fetch --unshallow

Update: I'm not sure if this was the same situation as what you ran into, but the GitKraken dev team responded to me saying the app doesn't support shallow copies yet: Why Gitkraken does not display any logs in big repos?

Answer 4

Run

git gc

from terminal and relaunch gitKraken worked for me.

See FAQ from gitKraken (https://support.gitkraken.com/faq/)

Answer 5

Fastest solution: reclone your repository from the remote server (Github, GitLab etc). The current local git repository could be corrupted for some reason. If you open both in git kraken you will see that the new local source will have visible commits.

Answer 6

I got the same issue, I already paid a one-year membership. So frustrated. I have to find another application instead of the gitkraken. I find Git Tower and Git Ahead.