![]() ![]() Itll crash, then reopen, but the preferences page wont appear. As I read in the document, it should first read the local one, then global, then system in order, so it should only read /etc/gitconfig if only can't find one in ~/.gitconfig, am I right? Why it isn't the case here? Or does GitKraken deliberately setting to read the config file from /etc/gitconfig first instead of the above order?Ĭonclude, I deleted the system gitconfig /etc/gitconfig (by renaming it to /etc/.gitconfig btw). GitKraken cannot see those repos when cloning or adding a fork unless the org specifically gives permission to GitKraken as an application. Things are working great for the most part, but GitKraken keeps crashing when I attempt to open the 'Preferences' page. ![]() This will allow you to either Open an existing repository, or Clone a repository that you or someone else has. GitKraken Client lets you open your repo in your default external editor, like VS Code, from the command palette. But I think it's just a workaround, I don't know what's the consequence of doing this (deleting system gitconfig). Click on the folder icon at the top left corner. And yet after deleting /etc/gitconfig, it works (I can clone my repo as expected). Then I thought "aha, I could just delete the /etc/gitconfig, then Kraken will use ~/.gitconfig". git/gitconfig), global (in ~/.gitconfig) and system (in /etc/gitconfig). I then kept googling, then I knew that there are 3 types of config files for git, which are local (located in. But after doing that, it still not work (permission denied), even after a reboot. After googling, I found a solution sounds rational is to type chmod 777 /etc/gitconfig to give everyone (includes GitKraken) the permission to read/write to that config file. Easily open repos, set favorites, and organize them in project groups. So I think GitKraken software needs to access a gitconfig file to get things work, and it somehow tried to access the one at /etc/gitconfig first (which is locked - I don't even know what "lock" mean), so it threw the error. GitKraken already has a project/repo open in the background that I cant. Often I will realise I need to check a different repo, open it (without remembering to start a new tab first), and then be frustrated by the previous repo I was working in no longer being open. I tried to clone a repo using GitKraken on Ubuntu, but it threw me an error "failed to open '/etc/gitconfig' - permission denied". Clone the project/repo to your machine from the GitLab server, using GitKraken. Either making 'opening a repo in a new tab' be the default 'open repo' behaviour - or at least allowing it to be a toggleable option - would be very convenient. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |