![]() ![]() Please forkive us for these bugs…they were preventing us from providing our knifest experience possible. We have added a loading icon to the left panel when adding a remote.The application size for GitKraken Client has been reduced by up to 30%.Memory consumption for GitKraken Client has been reduced by up to 20%.Application startup time for GitKraken Client has improved, making it up to 10% faster.And with reduced memory consumption and application size, you have more room on your plate for the good stuff. Some said it was too spoon to go for another performance improvement…but for fork’s sake, we just had to do it. ![]() GitKraken Client now supports core.longpaths, making it possible for Windows users to work with long paths exceeding 259 characters in length.If a fork does exist, GitKraken Client will offer to add your fork as a remote repository if a fork does not already exist, GitKraken Client will provide an option to fork the repository and add a newly created fork as a remote in GitKraken Client. Now, when adding a remote, GitKraken Client will check to see if a fork exists for your current repository. GitHub Users now have the ability to fork repositories from inside GitKraken Client.New ✨Īll we can say about these new features is….Fork Yeah! This latest update to GitKraken Client is so forking good, no one is going to judge you for fist pumping through your workflow. If GitKraken Client crashes, it will now automatically relaunch.The main process for MacOS users will now correctly display as “GitKraken” rather than “Electron.”.GitKraken Client will successfully perform a fetch, even if a pull request author has deleted their account on the related hosting service.If you cancel a rebase from GitKraken Client’s merge conflict tool, the tool will now reset properly.Now, when users rebase in GitKraken Client, the application will correctly remember your profile’s name and email address.We just had to break up with these bugs…it’s not us, it’s them. GitKraken Client will now remember the last directory to which you cloned a repository. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |