For users who prefer to compile their OS, Linux users should now be able to open their terminal from GitKraken Client.Windows users take a glass □: the Edit on Bitbucket Server button should no longer take you to a 404 page.Now you don’t have to be Sherlock Holmes the error message for creating a branch that conflicts with a branch directory is now clearly s-p-e-l-l-e-d-o-u-t-f-o-r-y-o-u.The keyboard shortcut to open history view has now been changed to Ctrl/ Cmd + Shift + H to not interfere with the “Hide” option on MacOS. Yes, we got up on the wrong hide of the bed.You could call it, a clean bill of help □. We nixed the 2 helpers who were sapping memory and system resources.rpm option for easy installation on CentOS, RHEL, or Fedora. For the 1 percenters, GitKraken Client now ships with a.The error message “ is not a function” will no longer appear when cloning or pushing from a TFS instance.The History and Blame buttons will no longer throw the error: “File path to get history is required.”.We all want to feel welcome, but Keif was getting a little carried away… Now, when opening a repository from the CLI using the -p argument, GitKraken Client will open the repository instead of the welcome screen.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |