And with reduced memory consumption and application size, you have more room on your plate for the good stuff. Improvements: - Some said it was too spoon to go for another performance improvement.but for fork’s sake, we just had to do it. GitKraken 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 will offer to add your fork as a remote repository if a fork does not already exist, GitKraken will provide an option to fork the repository and add a newly created fork as a remote in GitKraken. Now, when adding a remote, GitKraken will check to see if a fork exists for your current repository. GitKraken 6.5.2 (64-bit) Improvements: - Now, when users hover over the Push button in the toolbar, the upstream of the branch you’re pushing changes to will be displayed - GitKraken will now remember the last directory to which you cloned a repository Bug Fixes: - Now, when users rebase in GitKraken, the application will correctly remember your profile’s name and email address - If you cancel a rebase from GitKraken’s merge conflict tool, the tool will now reset properly - GitKraken will successfully perform a fetch, even if a pull request author has deleted their account on the related hosting service GitKraken 6.5.1 (64-bit) - If the GitKraken application crashes, it will now automatically relaunch GitKraken 6.5.0 (64-bit) New: - GitHub Users now have the ability to fork repositories from inside the GitKraken application. We have thoroughly investigated the issue and have verified the report was a false warning and GitKraken never contained a virus. GitKraken 6.5.3 (64-bit) Improvements: - For Windows users: We've addressed a false positive report from Windows Defender that GitKraken contained a Trojan virus. Windows XP / Vista / Windows 7 / Windows 8 / Windows 10
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |