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, July 12th, 2018
Bug Fixes 🐛
- Windows users experiencing an
Assertion Failed!error for
git_revwalk_hideshould no longer receive this error.
v3.6.6 does not include any changes to GitKraken Enterprise other than those listed above.
Monday, June 18th, 2018
- There are never too many places to add help instructions, so keyboard shortcuts are now accessible from the help menu.
- Like a veteran camera man tracking a through ball, checking out a branch through the Fuzzy Finder will now scroll the branch into view. ⚽
- GitLab.com users with private remote repositories will now display a placeholder icon instead of a blank box...a keeper, if you will.
Bug Fixes 🐛
- Hopefully we've fixed this one for good! Resolving merge conflicts on Windows should no longer result in the file getting CRLF line endings.
- On Windows, selecting View all files when viewing a commit diff should correctly display in Tree View. Or, if you're watching Mexico play, El Tri view. 🇲🇽
- Two World Cup games at the same time: awesome; two scroll bars at the same time: terrible. Long commit messages will no longer have double scroll bars when viewing the diff of a file.
- Can you imagine if two goals by the same player canceled each other out? A Pull Request with the same name as an existing Pull Request will now display, instead of appearing blank.
- Accurate passing is key to any match. When opening a Pull Request in GitKraken, using Tab will now jump to the next field instead of selecting users or labels from the dropdown menu.
- Pushing is grounds for a yellow card, so repositories with long names will no longer overflow in the repository bread-crumb menu.
- Like a super sub fresh off the bench, Enterprise clients that are launched in an offline environment should load significantly faster.🏃
Thursday, May 31st, 2018
- This release addresses the git vulnerability that was recently identified in CVE-2018-11235.
- GitKraken is not susceptible to CVE-2018-11233.
Tuesday, May 29th, 2018
Bug Fixes 🐛
- Hashtags are not just a commenting device: lesson learned. Commit messages with a
#will now only be commented out if the new comment option is enabled in your Preferences > Commit Template settings.
- Discarding or resetting an untracked or renamed file will no longer throw an error, especially since the action completes successfully.
- v3.6.2 does not include any changes to GitKraken Enterprise other than those listed above.
Tuesday, May 15th, 2018
- You may now disable spell check from Preferences > UI Preferences, and of course tell everyone about your spelling bee championship at Lincoln Elementary.
Bug Fixes 🐛
- If you installed the Linux
.debpackage recently, you may have noticed that GitKraken was not installed into your system path. We fixed that by pointing Keif back to the proper location.
- We popped the hood and made a change that allows for more memory allocatation when syncing with large LDAP environments.
Monday, April 30th, 2018
- Mission Control, we are a go for total pull request management! Users can now do the following when creating a pull request through GitKraken: 🚀
- GitHub.com & GitHub Enterprise:
- Add assignees
- Add reviewers
- Add labels
- GitLab.com & GitLab Self-hosted:
- Add an assignee
- Add labels
- GitHub.com & GitHub Enterprise:
- Is your pull request go for launch? GitHub users: GitKraken will now display the status of pull requests in the left panel. Hovering over a pull request will provide a summary of information on a build’s status.
- Typos can be costly, so we’ve added spell checking to the commit message box, pull request panel, and the commit template field.
- Quickly propel yourself into your repo folder from the new file menu option that allows you to open your repository folder in your default file manager.
- You can also use the keybind Alt + O.
- Reduce the drag on your graph by using the new context menu option to
Hide all tags
- Looking for more pull request info on the fly? Tooltips for open pull requests have been redesigned and should be easier to read.✨
- GitKraken will now display tag annotations. Let everyone know how amazing your code is 🔖
- Selecting the button from the Clone window will now take users to the hosting service tab instead of the general authentication tab.
- Switch repos at light speed! Ctrl/Cmd + Shift + O now opens the Fuzzy Finder with the open repo option preselected.
Bug Fixes 🐛
- You shouldn’t be faulted for writing a thorough commit message, so we resolved an issue that prevented users from accessing their submodules if the last commit message was very long.
- Amending a commit message using the commit keyboard shortcut should properly amend the commit instead of creating a new one.
- We managed to fit this one in: long branch names will no longer go off of the Git Flow panel.
- [GitLab Self-Hosted] users: Initializing a public repository through GitKraken would actually make the repository private; this has now been fixed.
- We’re all for resolving conflicts, especially ones that aren’t really there. For repositories on FAT32 or NTFS drives, GitKraken should now correctly checkout the branch instead of throwing conflict errors.
Thursday, April 5th, 2018
Bug Fixes 🐛
- GitKraken should now be able to connect to GitLab self-hosted servers with self-signed certificates, again.
v3.5.1 does not include any changes to GitKraken Enterprise other than those listed above.
Tuesday, March 27th, 2018
- Presto! Commit message D-N-A! You can now create commit message templates for each of your repositories. 🦖🦖
- For more information, check out our commit template documentation.
- For those times when you can’t network eight connection machines and debug two million lines of code all on your own, GitKraken will now display co-authored commits!
- Learn how to format co-authors in your commit message!
- Looking for that perfect iteration? We’ve added a context menu option to copy a commit SHA.
- Buried repos should stay buried; so GitKraken will no longer display archived GitLab repositories in the clone window.
- Since you can’t discard and stage hunks when viewing the diff of an untracked, removed, or renamed file, we’ve eliminated the temptation by removing those buttons.
- We consulted a mathematician and fixed the selection algorithm for unstaged/staged files, so it now respects Z-A sorting.
- Must code faster, must code faster! GitKraken will now perform an LFS pull after a clone or submodule initialization, when necessary.
- You don’t always have to force reboot the system, but you might need to force push some commits. For VSTS users, force pushing to a branch when you do not have the force push permission enabled will now provide a more detailed error message.
Bug Fixes 🐛
- That is one big pile of commits. The squash option should now appear after rebasing commits.
- Life...finds a way... Just like Keif has found a way to fetch PRs from a repository that is in a nested group on GitLab.
- T-Rex is much shorter, but we realize you can’t always abbreviate. Profiles with long email addresses and names should no longer be cut off in the dropdown menu.
- Nuh-uh-uh, you didn’t say the magic word! The Repository Management window will no longer freeze up after removing an account from the initialize repository form.
- WIP changes shouldn’t go extinct. Starting a new Gitflow branch would cause some WIP changes to vanish—that should no longer happen.
- Commit selection shouldn’t have to be explained by chaos theory. So
Shift + clickbetween two commits should now select all commits in between the selection instead of randomly omitting a few.
v3.5.0 does not include any changes to GitKraken Enterprise other than those listed above.
Wednesday, March 14th, 2018
Bug Fixes 🐛
- GitKraken should no longer throw the following error when fetching pull requests from VSTS:
Fetching pull requests failed. A project name is required in order to reference a git repository by name.
v3.4.1 does not include any changes to GitKraken Enterprise other than those listed above.
Wednesday, March 7th, 2018
- From the depths, a magical window has opened! GitKraken now integrates with Visual Studio Team Services (VSTS)! 🎉
- GitKraken Pro feature - Upgrade now to access!
- We like to Add/Remove Programs, too, so GitKraken now supports Araxis and P4Merge as external diff/merge tools.
- For the hover explorers out there, a tooltip has been added to the green check mark in the left panel.
Bug Fixes 🐛
- Integration help links will now send you to the correct support page instead of a 404 page...and it wasn’t even the fun 404 page; our apologies!
- Resolved an issue that prevented GitKraken from opening repositories that had a tag named
X. You probably figured it was the ‘X’ tag in your repo, huh?
- Toss those unwanted hunks out the window with confidence! Discarding hunks on Windows will no longer add LF line endings to a file with CRLF endings.
- Beta Feature: GitKraken Enterprise can now be configured to use LDAP as an alternative authentication method. 👏
Monday, January 29th, 2018
You might see a shiny new menu button. Only click it if you're ready to Glo!
- When discarding a single file through the context menu, you’ll now see a confirmation prompt: also known as the ohnoididntmeantoclickthat prompt.
v3.3.4 does not include any changes to GitKraken Enterprise other than those listed above.
Monday, January 22nd, 2018
- Keif’s New Year’s resolution was to be less secretive. So, hovering over a repository in the breadcrumb menu will now display a tooltip with the repository’s full path. 📁
- After some year-end reflection, Keif decided that when staging or unstaging from a list of files, GitKraken will now select the next item in the list instead of selecting the first file in the list. 🎉
Bug Fixes 🐛
- The feedback and support forms should no longer feel laggy when writing in the subject field… We do want your feedback, we promise!
- Scrolling through the Fuzzy Finder with your mouse wheel should now work as intended and not—you know—erase the results and act all weird.
- Making changes requires commit-ment, so we resolved an issue that prevented some users from entering a commit message after popping a stash.
- After staging, unstaging, or discarding all hunks and lines for a given file, GitKraken will no longer get stuck on a loading icon when trying to display the next diff. New year, new kraken! Keif will move on. 👏
- To make a change, you need to start from the beginning. So when editing a submodule’s URL, the cursor will no longer jump to the end of the URL.
- Wiki repos on GitLab are special. We know this now, and GitKraken will no longer display a “Fetching pull requests failed” toast when performing a fetch on a GitLab self-hosted Wiki repository.
v3.3.3 does not include any changes to GitKraken Enterprise other than those listed above.
Thursday, December 14th, 2017
Bug Fixes 🐛
- Users running Git hooks on OSX High Sierra may now commit. We've figured out our commitment issues 💍
v3.3.2 does not include any changes to GitKraken Enterprise other than those listed above.
Wednesday, December 6th, 2017
- Lost in a holidaze of commits? There's now a Fuzzy Finder shortcut to view working directory changes.🔍
- For our ambitious GitLab integration users with more than 100 repositories, you should now be able to see all repositories.💯
feature/cantremember? When creating a branch or tag, GitKraken will now leave the input field open if you navigate to a different window.
- We removed some of the...grey areas (sigh) by replacing the greyed-out placeholder text with actual placeholder text in the Clone and Init repository windows.
- We know everyone loves a cryptic error message, but they are now more descriptive when trying to initialize a repository on GitLab Enterprise. Sorry not sorry.
- We realized you need more than one character for a commit message, so GitKraken now allows users to write a full commit message after undoing a commit.
- When fetching from a GitLab repository, with merge requests disabled, an error message would appear saying it could not load your merge requests… GitKraken now understands this is the same as informing someone that something divided by 1 is itself.
- GitKraken will now properly cache group information for GitLab instead of constantly pestering the server about the same groups.
- Remotes on GitLab self-hosted accounts will now display the GitLab icon instead of the associated remote avatar. Trust us, it's better this way.
v3.3.1 does not include any changes to GitKraken Enterprise other than those listed above.
Monday, November 27th, 2017
- GitKraken now integrates with GitLab Community Edition and Enterprise Edition (Pro users only). 🎉
- When renaming a branch, the current branch name will now pre-populate the input field.
- We’ve added a context menu option to copy a file’s full path from the commit panel.
- Hovering over a user’s gravatar in the graph will now display a tooltip with that user’s name (or email if no name is provided).
- A loading icon has been added to the clone repository window; it displays while GitKraken is retrieving your remote repositories.
Bug Fixes 🐛
- New connections to GitHub Enterprise no longer require GitKraken to restart.
- Pull requests on GitHub.com with multiple assignees will now show all assignees in the tooltip and consistently display in bold when you are one of the assignees. (Previously, it would only bold if you were the first assignee.)
- Users will no longer be prevented from discarding changes for a removed file.
- In tree view, the commit panel should now properly display which files have been added/modified/removed/renamed while navigating through the graph.
v3.3.0 does not include any changes to GitKraken Enterprise other than those listed above.
Monday, November 13th, 2017
- Got GitLab.com? Now you may create a pull request and add a remote from GitKraken.
- The currently opened repository is part of the repository management window. 👏
- Esc will close the Gitflow and pull request panels.
- Attempting to delete a primary remote branch now creates a specific error message.
Bug Fixes 🐛
- Cloning and working with a LFS repository on Linux via SSH works now.
v3.2.2 does not include any changes to GitKraken Enterprise other than those listed above.
Monday, October 30th, 2017
- Fixed a bug in analytics that caused certain clients to over-report analytics data
Friday, October 26th, 2017
- If you have children, it’s usually a bad idea to have a favorite child. With GitKraken, it is totally fine to have a favorite repository, and thus we introduce you to the new Favorites list!
- Multi-select for discarding changes: like multi-select for Staging and Unstaging, but with Discard. 🗑️ We’ve added a context menu, too, so now you may discard all changes within a folder if you are in tree view. Brought to you by popular demand- we know how much you love multi-select!
- We’ve added a context menu option for updating submodules.
- Now use Ctrl+D(Windows/Linux)/Cmd+D(Mac) or the Fuzzy Finder to open your configured external diff/merge tool.
- GitKraken no longer displays a
Pushed Successfullymessage if a push fails due to a server hook. In other words, force-pushing to a protected branch will now display an error message instead of a false “success” message.
- We resolved an issue that would cause GitKraken to launch outside of your window region. Sorry about that, it won’t happen again. 💐
- Hitting the cancel button when trying to finish a Gitflow action (Hotfix, Release, or Feature) now properly closes the Gitflow window (instead of doing nothing).
- Discard all now discards submodule changes, too.
- GitKraken now correctly applies the operating system’s newline character when modifying a repository’s
- v3.2 does not include any changes to GitKraken Enterprise other than those listed above.
Monday, October 16th, 2017
- Context menu option added: copy your selection when in File View. For those of you who cleverly tried to use Ctrl+C(Windows + Linux)/Cmd+C(Mac), you will no longer get line numbers when pasting the file contents. 👏
- You can now initialize a repo with LFS and access the LFS configuration menu through the Fuzzy Finder.
- We’ve added small loading icons when Staging/Unstaging a file.
Bug Fixes 🐛
- Esc will once again close the preference menu. 🎉
- Drag and drop actions, as well as selecting text in the output panel of the merge conflict editor, are now more accurate when zooming above or below 100%.
- So long useless error messages: staging a file directory change, an additional change to an untracked file, or a renamed file no longer throws a meaningless error message. 👋🏼
- Fixed an issue which prevented filemode changes from being discarded if the change was still unstaged.
- Resolved an issue that prevented changes from being committed to a submodule that had post-commit hooks.
- The Git Config Default setting for external merge and diff tools now works with tools whose absolute paths contain spaces. Welcome, space! 🌌
From this release forward, any changes to GitKraken Enterprise will be noted here. v3.1.2 does not include any changes to GK Enterprise other than those listed above… but stay tuned! 🎆
Monday, October 9th, 2017
- GitKraken CPU & memory sea monster harpooned. 🌊
- Checkout and viewing a diff no longer results in GitKraken freezing.
- Discard hunk issue: now discards only the hunk, instead of the entire file. 😂
Tuesday, October 3rd, 2017
Did you ever see such a beautiful GitKraken? Introducing Keiferella! Our bibbidi-bobbidi GUI!
- We’ve given the commit panel a Cinderella-style makeover! 👸 It has a new header and can be pinned to the right or bottom of the window as you prefer.
- The “Discard All” button has been replaced with a trash can icon on the left side of the new panel header. This should reduce the chance of accidentally clicking it when staging changes.
💫 _Wash the dishes, do the dusting,
Do the staging, make the commits! _ 💫
- When viewing a commit, the SHA for that commit is displayed in the new panel header (and copyable with a click).
- When viewing the working directory, the new panel header will tell you how many files have been changed and display the name of the branch styled to match the label in the graph.
- When in a conflicted state, messaging will now correctly reflect whether the state was the result of a rebase or a merge. The branches involved are now also styled to match their labels in the graph.
- The list/tree view dropdown menu has been replaced with a new toggle button.
- Quickly jump to your working directory when viewing older commits, with a new shortcut that appears at the top of the commit panel.
- Now you can collapse the unstaged and staged files sections to make more room for viewing file changes in the commit panel.
- A checkbox to view all files is now available when viewing a previous commit. This allows you to browse and view all files in a repository as they were at that commit.
- External diff tools are now supported. Set the tool you prefer to use for viewing diffs in Preferences > General.
- We added a context menu option to copy a branch’s name from the left panel or the graph.
- There’s now a full-file contents view when viewing a diff of a commit. Users are able to toggle between viewing solely the diff hunks with changes, or the entire file with the changes applied.
This makeover came with new and improved easy-to-see scrollbars! 📜
But the thingamabob that does the job is bibbidi-bobbidi-boo.
- Background colors and other styling has been improved for both light and dark themes wherever code is displayed (e.g., the new full file contents view, the diff view, file history view, and the conflict resolution tool). This should make code easier to read by improving text contrast and further differentiating code views from other panels in the application.
- Linux users, this one’s for you! Update buttons are much easier to see now.
- Links to the EULA will now correctly take you to our EULA page (previously, it would do nothing… whomp, whomp).
- Once upon a time, in Windows, GitKraken would occasionally crash when viewing a diff. Issue addressed.
Wednesday, September 27th, 2017
- GitKraken will correctly generate 2048-bit SSH keys (issue caused GitKraken to generate 1024-bit keys).
- Git hooks will no longer fail if the path they are on contains spaces.
Monday, September 18th, 2017
- GitKraken previously only supported Git LFS up to a file size limit of
250 MB/file. The issue has been addressed and you may now use larger files (up to Git LFS's limit of
Wednesday, September 6th, 2017
Would you like some large files with that??
- Super size those files: Git LFS support has arrived! 🎉
- You can now select multiple files faster than going through the drive-thru! Simply use Shift or Control/CMD to multi-select files to perform any of the following actions:
- Context menus
- The right panel was looking a little beefy under the hood, so we slimmed it down a quarter pound and optimized the following:
- File Tree view navigation with arrow keys
- Scrolling through the file list
- Repository deletion should provide an error message if there is a file lock(s) preventing deletion.
- LFS file size limit:
250 MB/file. Don't worry, we're on it!