Obviously I was using an older version that’s why the feature was still working for me.Īs I said at the beginning of the post, I can’t say that this is “unexpected” because there is a company behind and companies need to profit. Also, there are some other points which were changed as well. Visiting the Axosoft blog, which is the company behind GitKraken, there is a post clarifying the situation, that is, private repositories will no longer be part of the free application as of version 6.0. The question that remains is, why was there no warning on the interface alerting users about that change?Īnyway, I went to the “GitKraken” website to understand what happened, hoping to find a release note, but right away I found nothing and ended up going to some communities where I finally found something. It doesn’t take a lot of neurons to understand that they took away one of the features that were “free” in one of those updates. The fact is that this weekend, a long time after I was using GitKraken, I came across an alert saying that I could not open my repository because it was private. The reason was pretty simple, in my point of view, GitKraken was more didactic and have a very easy and nice user interface. A simple search on google, returned me several client options and one of them was GitKraken, the option that I chose. I wasn't okay with that.The subject that I will approach in this post today took me by surprise, although I can’t say that it was an unexpected event, in order to better understand it, I need to tell a brief story.Ī bit over 1 year ago I’ve migrated my development environment from Windows (10) to Linux Mint.Īs expected, some tools are not compatible with both operating systems, so I had to look for alternatives to meet my needs.Īmong those needs was a GIT client as I honestly am not a big fan of handling everything by command line. 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. Those are temp files that should have been filled with data or deleted but were not, for. 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |