![]() ![]() 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. The links can be found in GitKraken Client’s context menus under Copy link to remote/commit. When specifying a branch, the latest commit of that branch will be focused. The links will focus GitKraken Client on the commit, branch, or tag specified. 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 Based on project statistics from the GitHub repository for the npm package gitkraken-i18n, we found that it has been starred 6 times. When shared, these links will both open and focus GitKraken Client to the linked repository. I receive a 'Could not find a compatible repository' for one of my repos. 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. That might be why GitKraken refuses to open such repositories: no working tree to work with. Generally, Docker supports pipelining only from GitHub & BitBucket, unfortunately, with GitLab, you need to set up this pipeline from your GitLab repo itself and not from Docker. I also found some zero byte objects, which should not be. It is important to specify in every pull and push in the scenario. Restart GitKraken Client and authenticate normally. Click on free icon in bottom right, this brings up a web page inside GitKraken Client which authenticates against Zscaler. The corrupted lines in my log had loads of strange symbols and were like 4 time the length of the other lines. Solution: If you have any of the above in place try the following: Sign in with GitHub authentication. 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. It is a much better version than the regular git clients you can get for free. Other tools (Giggle, gitg, git-gui, and the git CLI) all seemed to work just fine. Gitkraken is the best tool to manage the GitHub repositories and code. 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. |