Behold the evolution of GitKraken Client! 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.
Monday, December 5, 2016
Bugfix Fix Release
- Oh dear. Our 1.9.2 update broke fetching, pushing and pulling when connecting to hosts without GitKraken Client integration (GitLab, etc). This should now be working as expected.
Monday, December 5, 2016
- The context menu for stashes took an unexpected sabbatical in 1.9.1, but now it’s back and better than ever!
- Some users have been harassed by a persistent message, telling them that their Bitbucket tokens “need more permissions.” It’ll no longer pester you, promise.
- The GitKraken Store was stubbornly caching data. We’ve cleaned that up, because if we add a comma somewhere, you deserve to see that comma right away!
Tuesday, November 15, 2016
- Uh oh. GitKraken Client would spring a memory leak for some users when the commit list was updated, negatively affecting performance, hogging system memory and raining on the performance parade in general. We prioritized fixing that issue, sorry.
- Avast me hearties! If ye be sailing these SSH high seas, in some cases, the port number would disappear from your URI (
U R AYE!). Arr, we’d be a bunch of scallywags if we didn’t fix that, so we’ve made that bug walk the plank into shark infested waters! Arrrr. It be smooth sailing through your ports now, scoundrels.
- Did we mention the memory thing already? Something about a leak. Can’t remember.
Wednesday, November 2, 2016
This is the release for GitHub Enterprise. Its continuing mission: to allow for locally hosted GitHub accounts; to seek out new connection possibilities in a civilized manner; to boldly work where no client has worked before.
GitHub Enterprise support! Pro Feature
If you’re using GitHub’s self-hosted platform, GitKraken Client will play nicely with it. It won’t snatch, won’t throw tantrums, and it will share. In fact, it will offer you all the features that make working with regular GitHub.com services in GitKraken Client so seamless, without having to leave the app:
- Create pull requests
- Create repositories including .gitignore and license files
- Generate and verify SSH keys
- Save authentication into profiles
- Clone from GitHub Enterprise repo list
- Add remote repos
Those of you on 64-bit Windows can now download a 64-bit version of GitKraken Client! Wrap your tentacles around it here. The app also displays which version (32- or 64-bit) you are running, for reference.
Tag folders: Just as with branch folders, you can now keep your tags in an organized and visually tidy order with tag folders. Ah, that’s better!
Remember the left panel search? Well, now, when you type, the search term you’re typing will be highlighted in the filtered items. This is for your eyeballs. We hope they find it useful.
- Error log, supplemental: The crew has been alerted to a strange phenomenon resulting in cryptic messages about
included in other scopes. We sent an away team to investigate these
scopes, their customs and their weaponry, and it would appear that the crew is now returning to normal, thanks to GitKraken Engineering.
- The GitFlow panel static path prefix is now correctly, vertically aligned with the rest of the text. Yes, these minor imperfections add a certain charm and gritty character to the app, but it’s better this way.
- Left panel style tweaks to make you smile more or grimace less.
- Attempting to add an external SSH key to a service would initiate a super secret and unintentional broken SSH mode that nobody wanted.
Cannot read property ‘deletePassword’ of undefined.Absolute classic. You’ll miss that one, now that it’s gone.
Monday, October 24, 2016
- There was some lag when typing in the commit message input field, but it now keeps up with the fracking pace, thank the Gods.
- The graph no longer renders while a repo is being opened, which makes the process a bit faster and less distracting.
- Pushes would sometimes fail with a
Cannot read property ‘cancelled’ of undefinedmessage. That was obstructive, unhelpfully ambiguous and a bit of a negative nelly kind of message. So depressing! So fixed!
- If you tried to focus the left panel filter when the left panel was hidden, it would unleash a whole world of nope where you’d not be able to refocus it. It now behaves as expected, sorry.
Monday, October 17, 2016
Folders, Filters and Fixes, Oh My!
GitKraken Client’s left panel has been even more improved with some big new features:
Branch folders: Branch structures are now represented in beautiful, intuitive folder systems. Rejoice! At a glance, you can now see your folders and subfolders as actual folders and–yes–subfolders. The logical, clear, hierarchical structure will bring a nice, orderly tear to your eye.
Button tooltips: Left panel buttons (such as the > for GitFlow or the + for add remote) now have cute little tooltips to confirm their function. Adorable!
Left panel filter: If you have a lot going on in your repo, finding relevant items can be complicated, resulting in copious scrolling, looking around, and frowning. GitKraken Client is designed to make you click and scroll less, not more, so we’ve worked hard on a new filter feature for the left panel. You can filter the entire panel, including:
- Pull requests
Use keyboard shortcut ⌘ | Ctrl + Shift + F, and start typing. At the risk of stating the obvious, hitting Esc will clear the filter.
- When making a pull request from within GitKraken Client, selecting a branch would make the text color go dark. Like,
same color as the backgrounddark. Weird. Fixed.
.git/configURL entries would cause some repos to fail to open. We’ve fixed that issue, because if you had to choose one thing you’d want GitKraken Client to do, it would probably be “open a repo.”
- When cloning a new repo and using GitKraken Client to create an initial commit, that repo’s remote would not show up in the UI, but it does now.
- Under some circumstances (involving team names and repo names in Bitbucket), GitKraken Client would fail to create Bitbucket pull requests. Where it once failed, GitKraken Client now succeeds!
- Let’s say you were able to make a Bitbucket pull request. Well, you were still not out of the woods, because some Bitbucket PRs would not show in the left panel even if they were successfully created. The left panel now shows them all.
- Relative commit dates in the graph were off by 1. If “off by 1” sounds like an unwelcome state of affairs, tha’’s because it is. And, as such, it has been fixed.
- For some users, the file history would serve up this bland message:
searched until invalid date (). Whatever that means, it’s not a message you’ll see anymore, thank goodness.
Wednesday, October 5, 2016
- We stopped the
WIPtext field from repopulating itself after a commit was made. That was pretty, pretty annoying, wasn’t it.
- We stopped along the road for a bite to eat. The cowboy went off to have a spare tire patched, and Eddie and I sat down in a kind of homemade diner, connected to the wifi and started up GitKraken Client. It crashed. I thought nothing crashed on a Mac; you could hear my raspy cries clear across the plains, across the whole gray world of them that day. A GitKraken dev came booming into the diner, calling my name, and he had the sweetest bugfixes.
“Rustled me up a terminal script to get rid of the
.DS_Storefile causing crashing issues on macOS.”
And he gave me this script, to manually delete the
.DS_Storefile that prevented startup and prevented auto-updates because the app wouldn’t start up to access those automatic updates.