Now, when adding a remote, GitKraken will check to see if a fork exists for your current repository. 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. GitKraken now supports core.longpaths, making it possible for Windows users to work with long paths exceeding 259 characters in length. Improvements: - Some said it was too spoon to go for another performance improvement.but for fork’s sake, we just had to do it. And with reduced memory consumption and application size, you have more room on your plate for the good stuff. Gitkraken cannot read property fullname of undefined update#Īpplication startup time for GitKraken has improved, making it up to 10% faster - Memory consumption for GitKraken has been reduced by up to 20% - The application size for GitKraken has been reduced by up to 30% - We have added a loading icon to the left panel when adding a remote Bug fixes: - Please forkive us for these bugs.they were preventing us from providing our knifest experience possible - If the left panel is collapsed, users can open all menu options - All rows will be styled correctly in Interactive Rebase view Enterprise: - Enterprise users running on Linux now have an option to Check for latest update in the File menu GitKraken 6.4.1 (32-bit) Bug fixes: - If stashes are created externally, users can now view the content of those stashes inside of GitKraken - Creating branches titled constructor or toString will no longer cause repositories to become invisible - GPG users using Git for Windows with non-empty passphrases will be prompted for their GPG passphrase instead of seeing the message: Error: GPG passphrase not found - Git Hook activity log tabs will no longer display the word Repository GitKraken 6.4.0 (32-bit) New: - A long time ago in a galaxy far, far away.was a Git GUI without activity logs - Introducing Activity Log! Users can now view all Git actions made to repositories and all application actions made in GitKraken through activity logs. Access this feature through the new icon in the footer toolbar - To access the activity log for a repository, navigate to the repo’s tab and click the icon. You will then see any Git actions made in the repo listed in chronological order on the tab titled Repository - To access the activity log of local application changes made in GitKraken, click the icon. Gitkraken cannot read property fullname of undefined update#.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |