To clone a remote repository over SSH, first navigate to your hosting service and copy the SSH link. Then go to GitKraken and clone the project through File Clone. Paste the URL, hit Clone the repo, and then open the repo in GitKraken. Supported SSH formats. The standard protocol can be entered as a remote in one of following formats. Later, you may find yourself using alternatives. GitHub is the market leader for open source projects and Julia, but there are other options, e.g. GitLab and Bitbucket. Instead of the GitHub Desktop, you may directly use the Git command line, GitKraken, or use the Git functionality built into editors such as Atom or VS Code. Explainer: When the window pops out saying that it could not find a compatible repository (local repository), chances are that you stashed your work on the other branch and then closed GitKraken which means, GitKraken might have lost the state of the repository.
- Gitkraken Couldn't Find Compatible Repository
- Gitkraken Could Not Find A Compatible Repository Form
- Gitkraken Could Not Find A Compatible Repository Using
I recently encountered an error in GitKraken after a bad merge occurred when trying to merge in some changes from the main development branch, whilst I had quite a few local changes that GitKraken usually automatically stashes for me.
My problem was I was using Bash Ubuntu on Windows, which has a nasty habit of locking files. The merge and stashing seemed to fail because in the changes I was attempting to merge in, some files were deleted.
I tried closing and reopening GitKraken, but it was clear that GitKraken wasn’t going to let me open up that repo again.
The fix
I realise this is a bit of a nuclear fix, but you’ll need to open up PowerShell to fix this. For me, it was simply a matter of navigating to the project directory and running: git reset --hard however, if you need changes, your repo will be interactable just fine on the command line.
As far as I could see with everything I tried, GitKraken won’t ever fix itself, the command line is the only solution. The above, once I ran it and opened up GitKraken it worked just fine again as nothing had happened.
; Date: Wed Feb 07 2018
Tags: GitKraken
GitKraken is a totally excellent Git client. If you're a software developer you should absolutely give GitKraken a try. Today I went to do some commits in one of my repositories but GitKraken told me it had gotten an Inotify Limit Error, and that I needed to increase this limit. Turns out the issue has nothing to do with GitKraken, and is also fairly easy to fix.
Upon opening the repository in question, GitKraken showed a notification window with this message:
Inotify Limit Error File watching is disabled for this repository. Please increase your inotify limit and reopen this repository.
Gitkraken Couldn't Find Compatible Repository
Previously in the day GitKraken gave a message while opening the same repository that it didn't find a 'Compatible Repository' and it refused to even open the repository. Thing is, the repository is fine, and I used git to do my commits without problem. It's possible the Inotify Limit made some kind of impact on GitKraken causing GitKraken to say it could not find a compatible repository. I've sent the GitKraken team a query and haven't received a reply.
An important detail is that I'm on Ubuntu 17.10. I've been using Mac OS X for many years, and recently setup this Ubuntu machine to see how well any kind of Linux would work for me. For what it's worth GitKraken is working the same on both, thanks to the portability coming from it being an Electron-based application.
From Wikipedia:
Inotify (inode notify) is a Linux kernel subsystem that acts to extend filesystems to notice changes to the filesystem, and report those changes to applications.
One major use is in desktop search utilities like Beagle, where its functionality permits reindexing of changed files without scanning the filesystem for changes every few minutes, which would be very inefficient.
Since GitKraken automagically notices changes in files in a workspace, it obviously must be using this subsystem on Linux. Since I'm using Ubuntu, this applies to me.
Type this command:
This is the limit on your computer.
Each inotify watch consumes a modest amount of memory. On a 64-bit computer like this one, each consumes 1 KB, so 8,192 watches consumes about 8 MB of memory. On a 16GB main memory computer that's a drop in the bucket.
Temporarily increasing the limit is this simple:
After which you'll get this:
To make a permanent change, set fs.inotify.max_user_watches= in sysctl settings. On some systems (Debian/Ubuntu/etc) those settings are in /etc/sysctl.conf and on some others there will be a file in /etc/sysctl.d.
After editing the sysctl settings, run this:
Gitkraken Could Not Find A Compatible Repository Form
Putting it on one line:
Or on certain other systems:
References:
Gitkraken Could Not Find A Compatible Repository Using
Please enable JavaScript to view the comments powered by Disqus.