Reputation: 377
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 Preferences". I tried to reinstall Gitkraken, reopen the repository and reboot xampp/my computer but it didn't work. My computer is a MacBook Pro (Retina, 13-inch, Early 2015) with macOS Mojave 10.14.6.
Upvotes: 23
Views: 18982
Reputation: 1
Had the same issue after my machine crashed and corrupted my repo. I opened the repo in Git GUI which detected some errors and offered to fix them. GitKraken worked fine after that.
Upvotes: 0
Reputation: 1
In my case, adding modified content and committing in the terminal fixed the problem. Clearly, my commit-graph was not that long.
Upvotes: 0
Reputation: 1
For me it was because of trying to commit node_modules folder. I've created .gitignore with node_modules in it and started working after restart of GitKraken
Upvotes: 0
Reputation: 1
"I successful recovery!"
You need clone the same local archival with other computer Another one you can go to your web (GitLab/GitHub...) download again your remote file
And then you should put in your new archival location then open the GitKraken change a "open a Repository"...
reloading...... "successful recovery!"
Upvotes: -1
Reputation: 96
Run
git gc
from terminal and relaunch gitKraken worked for me.
See FAQ from gitKraken (https://support.gitkraken.com/faq/)
Upvotes: 4
Reputation: 501
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.
Upvotes: 4
Reputation: 11
I deleted my repository and installed again. The error is gone.
Upvotes: 1
Reputation: 381
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.
Upvotes: 1
Reputation: 4110
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:
It is not the solution I hoped for but at least I did not lose the whole repository.
Upvotes: 1
Reputation: 616
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?
Upvotes: 10