![]() 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 To get my GitKraken working again, I need to go with the Nuclear Option. Make a symbolic link without a dot and open the repository via that. Those are temp files that should have been filled with data or deleted but were not, for. Gitkraken doesnt like the <.>.git in the directory path.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 wasn't okay with that.I just had this same issue with GitKraken. It is highly advised to make sure the project license is compatible with. 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 We couldnt find an appropriate license for this project. For macOS and Linux users: Close GitKraken. Keep in mind that this action will reset all of your GitKraken settings and preferences. gitkraken located in your home directory (macOS/Linux) or the APPDATA directory (Windows). To get my GitKraken working again, I need to go with the Nuclear Option. 30 Answers Sorted by: 44 A possible solution for resolving this issue with GitKraken is to delete the hidden folder. Those are temp files that should have been filled with data or deleted but were not, for. ![]() ![]() I just had this same issue with GitKraken.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |