GitKraken Current

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.


Version 2.1.0

Monday, February 13, 2017

New Features

  • Remote avatars: When multiple remotes were displayed on the same ref label, it would get hard to differentiate between them. In short, they were looking California and feeling Minnesota. Now each remote has its owner's avatar attached to it so you can clearly see the difference at a glance, even if you're searching with your good eye closed.
  • New remotes compatibility! Remotes on TFS 2015, TFS 2017, and VSTS that use HTTPS are now working.
  • You can now use GitKraken on computers behind non-authenticated proxies!
  • We've made significant performance improvements to the left panel. Especially with larger repos, you should notice snappier performance.

Bug Fixes

  • Repos with a large number of tags should be faster now.
  • The graph and the left panel were exhausting themselves by refreshing every time you blurred and then refocused the app, causing lag. Both the graph and the left panel have decided to chill and only refresh when absolutely necessary, meaning no more lag.
  • Scrolling to commits that are more than 2 rows outside the current view now puts them in the middle of the screen. Deleting a reference would sometimes seize up the process. You're busy, you don't have time for that. Tomfoolery begone!
  • Emojis are displayed on the graph again 🍆
  • Selecting multiple commits once again shows the author information for those commits.
  • We swapped the candy cane progress bars for the eye candy known as "Spinny Keif."
  • Showing a diff between 2 branches would sometimes do the precise opposite by showing nothing, because the app would crash. This is contrary to intentions and has been fixed.
  • You didn’t want two commits with identical timestamps to break the app. We get it. We fixed that. But maybe you're just too demanding, maybe you're just like my mother (she's never satisfied), why did we let this bug happen? This is what it sounds like, when devs cry.

Version 2.0.1

Bugfix Release - Wednesday, January 25, 2017

Sigh. It's the obligatory x.0.1 update to the major update, and now the whole tidiness of 2.0.0 is ruined. Great, just great. :slow clap:

Fixed

  • We understand that you need to open submodules, and now we are sure that you can, sorry!
  • Editing a submodule: This is a weird, weird thing that happened. So, here's the thing. If your submodule is in an OK state, editing that submodule would break the app. Now, it doesn't, which means we fixed it, and we are sorry it didn't work.
  • Setting upstream on a ref with a . in the name wouldn't work. . hardly seems like a far out there character to include in an upstream so we fixed that right up for you.

Version 2.0.0

Monday, January 23, 2017

Now, 2x Faster!
Like a kraken with a jetpack!

Hey there. How’s it going, champ? Did you enjoy the holidays? A safe and hopeful new year? It’s been a while. You know why? Because we’ve been working on a big one. The big 2.0. You probably know by now how we like to keep to a two-week development cycle, but for this release we made a decision: PERF, PERF and MORE PERF; work hard on performance overhauls, don’t release until it’s ready. The GitKraken team is proud to give you v2.0! You will find that everything is much more snappy than before. In some cases, operations are as much as 10x faster!

Usually we put our shiny new features at the top of the release notes, but with v2.0, the performance really shines, so let’s look at those items first.

Performance Improvements

  • Make a commit and watch GitKraken go! Committing is completed far quicker than in previous versions.
  • New year, new you: Open those repos at least 2 x faster than you could in 1.9.
  • Don’t forget to thank your grandma for the $5 in your Christmas card, and for drastically improving the scroll refresh in the graph. Did you see that? No more blank spots during scroll!
  • In fact, the graph scroll is also much, much faster. Do you scroll both ways? Great! Scrolling is noticeably faster on both axes.
  • Scrolling through a file’s changes is significantly faster, too.
  • Traversing the graph using keyboard shortcuts and the arrow keys was nice enough, but came with significant lag. Now it’s snappy and responsive.

New

  • .gitignore: A big feature request from our users is finally here! You can now select a file or folder in the file staging area, and add to the .gitignore file on the fly. Right-click and select Ignore. From there, you can:

    • Add that specific file to .gitignore
    • Add all files with that file extension to .gitignore
    • Add all files in the same folder as the selected file to .gitignore
    • (If selecting a folder) add that folder to the .gitignore
  • Psst. GitKraken’s a bit CLI-curious! There’s a new option to open the current repo folder in terminal. Just go to File Open Terminal or use the keyboard shortcuts opt + T (Mac) / alt + T (Windows + Linux).

  • Your drunk uncle might have all the great Christmas dinner stories, but can he push a commit and create a pull request at the same time? Only if he’s using GitKraken. If you haven’t yet pushed a branch to a remote, you can choose to push and start a pull request in one command. Saves clicks and time! Hic!
  • Open GitKraken! Go on, try it! Look at Keif swim with delight! Watch that smile and know that, today, you made one kraken very happy.
  • We polished up the visual feedback during loading operations in-app, too. Remember that embarrassing wobble in the previous version’s loady-spin? But a distant memory.

Improved

  • When you're setting an upstream, you can select from available remotes instead of having to type out the fork and remote like it’s 2016. The really neat part is that GitKraken will get the gist of your most popular upstreams, and then prioritize those in the drop-down. Of course, if you want to type, you can still type.
  • PRO: Profiles can once again be assigned discrete GitHub / Bitbucket accounts.
  • UI improvements:

    • New light and dark themes use a reduced color palette that is more consistent between themes. Notice that moodier, bluer tint to the dark theme? That was us.
    • A lot of love was given to the light theme to clean up the UI and improve contrast with a new color palette.
    • Input focus and mouseover styles have been added/modified to improve contrast and consistency.
    • Merge resolution tool UI has been cleaned up significantly, fixing alignment issues, etc.
    • Font style variations were reduced to improve legibility and generally look less wacky.
    • The font used to display code has been updated for legibility and is now consistent in all views.