GitKraken Release Notes
Behold the evolution of GitKraken! Find out what’s new, what’s fixed, or just take a trip down memory lane with a nostalgic swagger, remembering those bugs of yesterday.
Thursday, February 20th, 2020
- For Windows users: We've addressed a false positive report from Windows Defender that GitKraken contained a Trojan virus. We have thoroughly investigated the issue and have verified the report was a false warning and GitKraken never contained a virus.
Wednesday, February 19th, 2020
The latest updates to the GitKraken Git GUI are downright romantic - they might just octopi your heart for the rest of the month. 🐙💘
Don’t even try to tell us these improvements don’t tentacle your fancy…
- 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 🐛
We just had to break up with these bugs...it’s not us, it’s them. 💔
- 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.
Tuesday, January 28th, 2020
Bug Fixes 🐛
- The main process for MacOS users will now correctly display as “GitKraken” rather than “Electron.”
- If the GitKraken application crashes, it will now automatically relaunch.
Thursday, January 23rd, 2020
This latest update to the GitKraken Git GUI is so forking good, no one is going to judge you for fist pumping through your workflow.
All we can say about these new features is….Fork Yeah!
- GitHub Users now have the ability to fork repositories from inside the GitKraken application. 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.
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.
- Application 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 users running on Linux now have an option to Check for latest update in the File menu.
Thursday, December 19th, 2019
There’s no room for these bugs in our pear tree... 🎄
Bug Fixes 🐛
- If stashes are created externally, users can now view the content of those stashes inside of GitKraken.
- Creating branches titled
toStringwill 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.
Thursday, December 12th, 2019
It is a period of fast, constant Git actions.
GitKraken has risen victoriously over the
evil CLI. Save your teammates and restore
maximum productivity to the galaxy...
This release addresses critical Git security vulnerabilities. Immediate upgrade to GitKraken v6.4.0 is recommended. Please review this article for more information.
A long time ago in a galaxy far, far away...was a Git GUI without activity logs.
- Introducing Activity Logs! 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. You will then see all application changes listed in chronological order on the tab titled Application.
- The progress of Git hooks can also be tracked through activity logs. All Git hooks within the repository's log contain a clickable link where you can click to view the hook’s output in a separate tab.
We polished our lightsabers and dusted off our droids to make these improvements your new reality.
- The appearance of the dropdown menu that displays when selecting a repository to clone has been improved for consistency.
- We have added additional context to the error message that displays when opening a pull request with a remote ref that doesn’t exist.
- Commit author names are now displayed on hover above commit nodes in the graph instead of below them.
Bug Fixes 🐛
We built up a Resistance to these unwanted bugs.
- When opening GitKraken, if the most recent tab is not a Glo Boards tab, and the user switches to or opens a new Glo tab, the Glo Board is now correctly in focus.
- Commit search now closes upon opening the Fuzzy Finder.
- Editing a file to a previous state no longer creates an empty WIP node.
- Users cannot use keyboard shortcut Cmd/Ctrl + F to search commits when the graph is blocked by a prompt for input (as search results would not be visible behind the prompt’s display box).
- The button on a new tab now works as expected.
- Bitbucket remote origins now correctly display their name instead of displaying
- GitLab users can view and create pull requests from repositories in subgroups.
- Users will be appropriately directed to Account Management in the application after clicking during the free trial period.
- Users will no longer be prevented from interacting with collapsed left panel items.
- Users with multiple profiles can now successfully delete the first profile created from that account.
- Folders will be created when cloning a repository on Windows.
This release includes fixes for the following vulnerabilities:
Please review this article for more information.
Tuesday, November 5th, 2019
GitKraken comin’ at cha with some epic improvements and bug fixes courtesy of our v6.3.1 release.
- Users now have the ability to force push tags. The action will trigger a warning message.
- Pushing a tag to all remotes is faster.
Bug Fixes 🐛
- MacOS Catalina users can access the terminal option.
- Initializing a repository inside of GitKraken no longer causes an empty screen to display.
- Interacting with a remote host or proxy that is self-signed will no longer cause the error message:
Failed to get server certificate: The handle is in the wrong state for the requested operation.
- Users can successfully checkout a submodule change where the URL has been modified.
Monday, October 14th, 2019
Dun nuh nuh nuh 👏👏 Dun nuh nuh nuh 👏👏 Our GitKraken team is kooky, these new updates are so good they’re almost spooky. We’re all ready to scream ‘“whoopee!” The Kraken Family.
No need to hold a séance, this new search feature will help you conjure those spirits. Uncle Fester...is that you?
- Users can now associate Glo cards with pull requests created from within the GitKraken Git Client. When creating a new pull request, simply search for the Glo card you wish to associate. The pull request description will then be updated to include a link to said card. Better yet, if you’ve set up the GitHub pull request integration, you can trigger an automatic change to progress your card to a new column the moment your PR status changes.
- Users can now control the max number of commits that display in your graph. Navigate to Preferences → General and set a value for
Max Commits in Graph. You will also see an option to
Show All Commits in Graph.
We brought in Gomez and Morticia to class this place up with some supernatural improvements.
- Users can now resize the text field to amend commit messages, and the and buttons are now closer to the text field.
- SSH keys using the OpenSSH format are now supported.
Bug Fixes 🐛
With Lurch’s help, we’ve banished these bugs back to the cemetery.
- Users can successfully drag-and-drop remote references to generate the menu option to start a pull request.
- Users can switch tabs without the operation feeling sluggish.
- Initials will correctly display inside of
Blame Viewinstead of Gravatar images when the
Display author initials instead of avatarsoption is selected.
- Keyboard shortcuts for Glo will now work after switching to a Glo tab.
- If Glo is unreachable from the GitKraken Client, the application will correctly timeout and show an error message instead of hanging indefinitely.
Wednesday, September 25th, 2019
👻 The GitKraken team has released the ghouls of Sleepy Hollow to add some spooky new features, improvements, and bug fixes to version 6.2.1 of our Git client.
The headless horseman is on the move...and all that’s left of Ichabod Crane is a shattered pumpkin. 🎃
- Users can now enter a detached HEAD state by clicking the commit you wish to checkout and selecting
Checkout this commit.
- The editor line endings preference will only apply to new files created in GitKraken.
Bug Fixes 🕷
- Users can successfully clone a repository with a space in the name over HTTPS when using the Azure DevOps integration.
- The initialize submodule prompt will work properly after cloning a repository with submodules.
- Unstaged diffs for submodules will display accurately.
- Loading a diff will no longer cause the application to crash.
Wednesday, September 11th, 2019
You don’t need to throw down like James Bond at the Monte Carlo to feel like a winner; just check out these latest GitKraken features, improvements, and bug fixes.
The country might be small, but its fortunes large. Trust us, this new GitKraken feature calls for a top-shelf martini. Shaken...not stirred. 🍸
- The GitKraken merge conflict tool and built-in code editor have been updated with performance improvements affecting scrolling, output editing, and conflict line selection. The GitKraken merge tool now utilizes Monaco Editor, the same editor found in VS Code, which gives users the ability to independently search within the three separate conflict windows using the keyboard shortcut Cmd/Ctrl + F. Extra gold for Paid users: the code editor’s output now has auto-complete capability.
These latest improvements to the GitKraken Git Client are shocking...positively shocking.
- Significant UI improvements have been made to the commit panel, including more recognizable file status icons, easier view of file names, and more.
- Escape guarding has been added to the Pull Request panel. Now, if you add text in any field on the PR template form, you will not be able to close the panel without clicking the X button at the top right of the panel.
- Users can again push a tag after it has been moved locally.
- GitKraken will now select the
WIPnode instead of the
HEADnode when detecting a merge conflict.
Bug Fixes 🐛
Because a world with these bugs is not enough… M’s orders
- Date and time settings set by the user will now be respected.
- When trying to pop a stash created from outside of GitKraken, users will no longer receive an error message.
- If the commit message is empty, the
create commitkeyboard shortcut will no longer create a commit.
- Unless the diff view has been focused, Esc will close the diff views.
- Creating a workflow with the same file name as an existing workflow will no longer close the GitHub Actions panel.
Ignore and stop trackingfeature will now correctly remove the ignored file from the index.
- When editing a file inside of GitKraken using our code editor, a user’s line ending preference will apply the correct line ending.
- When merging two conflicting branches, the correct commit message will now be generated.
- Users no longer need to hit the Save button twice when closing the merge conflict tool.
Wednesday, August 21st, 2019
🚌We went back to the blackboard to come up with these GitKraken improvements, bug fixes, and updates to our Enterprise Git Client. 👩🏫
We’re going for the Dean’s List with this improvement. ⭐️
- Stashing time has been improved for stashing staged files.
Bug Fixes 🐛
🙅 These bugs have been expelled from campus!
- Users can again create a remote repository and clone it using an integration.
- The Commit Search will return expected results when a stem word is queried.
A+ grades across the board for these updates to our Enterprise Git Client. 👏
- The option to Sign in with GitHub has been removed.
- The Linux Enterprise Client will now update properly.
Thursday, August 15th, 2019
Bug Fixes 🐛
The Electron cache now clears automatically with each update to ensure Glo tabs load correctly.
Wednesday, August 14th, 2019
We’ll have you singing Hakuna Matata with these GitKraken v6.1.2 updates. 🎉
🦍The baboons are going ape over this improvement.
- The performance of GitKraken’s stashing functionality has been improved.
Bug Fixes 🐛
We respect all living creatures, from the crawling ant to the leaping antelope, but this bug got to go -- sorry Pumba! 🐗
- The libgit2 version has been updated to address a recent security patch.
Friday, August 9th, 2019
Bug Fixes 🐛
- Users behind an authenticated proxy will now see a prompt for their credentials inside of the Release Notes & Glo tabs.
- Renamed the duplicate GitLab.com option under Preferences → Authentication back to GitLab (Self-Managed).
Thursday, August 8th, 2019
No matter what Chu were hoping for, these new GitKraken features, improvements, and bug fixes are cause for celebration. 🎉
🔎 Get out your magnifying glass and prepare to search like you never have before, Detective.
- Users can now easily search inside the graph for commits by message, author, or SHA. Access this feature with the keyboard shortcut Ctrl/Cmd + F or click on the toolbar’s search icon. While searching, use Enter or ↓ to view the next result in the graph, or Shift + Enter or ↑ to view the previous result.
- New GitHub Actions integration! Users can now add, edit, and delete GitHub Actions workflows inside of GitKraken. The GitHub Actions section will appear in the left panel for repositories with a GitHub upstream or any repository with the
.github/workflowsdirectory. Choose from several workflow templates to get started.
We might not have a thunderstone, but we’ve leveled-up GitKraken with these improvements. 🆙
- The integration tabs under Preferences → Authentication have been changed to a vertical layout.
- The merge conflict warning when opening a pull request will now display a list of conflicted files.
- An un-bundled version of GitKraken’s strings file has been added. Users can edit/replace for use in non-officially supported languages. This file can be located at
- More Keif avatars have been added to profiles.
- An option has been added to the Fuzzy Finder to view GitKraken release notes.
Bug Fixes 🐛
⚡️Our small yellow friend helped us thunder shock these bugs into oblivion.
- Users will no longer encounter the error message caused by .gitignore negation rules,
Checkout failed: error matching pattern due to .gitignore, when checking out a branch.
- Users can now change the project group name casing when renaming a project group.
- When initiating a push and pull request through the context menu, the Pull Request panel will now appear once the local branch has finished pushing to your remote.
- The reset branch context menu will now perform as expected after dragging a branch onto another reference in the graph.
- We (really) have fixed an issue with authentication for Bitbucket servers when the username is an email address.
Thursday, July 18th, 2019
Warning: Endgame Spoilers Ahead (oh and get out from under that rock and go see the movie!)
After our epic v6 release, we still had some webs to untangle. After all: with great power, comes great responsibility.
It might take some time to get used to these new
powers features, but we’re confident you’ll be shooting webs from your hands in no time.
- This one’s for you Aunt May. Users can now configure the location of notifications in GitKraken by going to Preferences -> UI Preferences -> Notification Location.
- The message box for commits is now resizeable.
- Users can now use the keyboard shortcut Shift + J (or Shift + ↓) to jump to the parent commit of a selected commit.
- Similarly, users can also use the keyboard shortcut Shift + K (or Shift + ↑) to jump to the child commit of a selected commit. No webs required.
Like Spidey’s new suit, it’s as if Stark himself helped with these technical improvements (we miss you Tony!)
- The Fuzzy Finder will now filter search results based on frequency of function use.
- When you hover over an author/committer name, a tooltip of their email address will display in the commit panel.
- A caps lock warning notification will now appear in all password input fields.
- A tooltip has been added to Project Groups to display the directory path.
Bug Fixes 🕷
We got some help from our friendly neighborhood Spider-Man to control the GitKraken bug population.
- Now, if there is a corrupt reference in the repository, the graph and its branches will still display.
- The Commit Changes context menu and button options for submodules will now work properly.
- GitKraken will no longer take an extended time to timeout when switching to a tab with an inaccessible remote repository.
- Users can now focus the Fuzzy Finder search box by selecting the search commit icon.
- Extra new tabs will no longer generate when relaunching GitKraken if you have the Remember Tabs setting disabled.
- The Mac keyboard shortcut Cmd + Q will quit GitKraken if Glo is open.
- Bitbucket Server users who have email addresses for their usernames can now successfully integrate their repositories.
- Merge commits will no longer have unknown authors if the global gitconfig has no email address.
- Resolved an issue where files from a different branch would appear in the working directory if a user performed a branch checkout through the CLI.
Monday, June 17th, 2019
Start your engines and prepare to blast off with our v6.0 perf improvements. You’re going to want to buckle your seatbelts...Nic Cage is at the wheel. ⏩⏩⏩
No need to keep Tabs on this journey. Launch systems are a go. 3. 2. 1…... 🚀🚀🚀
- TABS...sip, ah. The speed and performance improvements involved in v6.0 has finally made switching between multiple repos in the form of tabs possible! Users can also use Tabs to switch between repos and Glo Boards.
- If a merge conflict exists between your source and the target branch, a
Merge Conflict Detected!error message will now directly appear in the pull request template panel when attempting to initiate a pull request.
Like a Nascar pit crew, our team spruced up the physical performance of GitKraken to achieve peak racing form. Prepare for lightspeed… 🏎💨
- The startup time of GitKraken is up to 2.3x as fast!
- The application size has been reduced by approximately 100MB for MacOS users.
- It will feel like taking a Buggati for a spin. Checkout in LFS is now 14x as fast!
- Newly created pull requests will display much faster.
- Toast notifications have been moved from the upper right corner to the lower left corner of the central UI to avoid blocking important information.
- File History and Blame views load up to 20x as fast! Top that Usain!
Bug Fixes 🐛
Flash! We’ve zapped these slow pokes out the way! ⚡️
- Users will no longer encounter the error message
Cannot read property isGitHookError of undefinedwhen finishing a release branch through GitFlow.
- Commits will no longer appear detached from their respective branch if a child commit’s date is older than the parent’s commit date.
- Self-hosted remote services with a domain containing a custom port or path will now be supported through GitKraken’s integration feature.
- All folders in Tree View can now be expanded.
- When using the Bitbucket.org integration, duplicate repositories will no longer appear in the clone menu.
- When using the Azure DevOps integration, repositories will be listed alphabetically on the clone menu.
- Users with their
inputwill no longer have line endings converted to
CRLFwhen resolving a conflict.
- Submodules will no longer be not initialized after discarding submodule changes.
- Commit message text now wraps correctly inside of the commit message box.
- Several GPG-related bug fixes have been applied, including:
- All merge conflicts will now be signed after selecting the Sign commits by default checkbox.
- The error notification message will be more descriptive when attempting to generate a GPG key with a name not provided in a user’s profile.
- If using older versions of GPG, users will no longer encounter a
gpg: invalid option --pinentry-modeerror notification.
- Annotated tags on Windows will now be correctly signed.