軟體下載 GitKraken 3.5.0 (32-bit)

• 1

  版本確認

• 2

  檔案準備中

• 3

  檔案下載

What's new in this version:

GitKraken 3.5.0 (32-bit)

Features:
- Presto! Commit message D-N-A! You can now create commit message templates for each of your repositories
- 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

Improvements:
- 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 + click between two commits should now select all commits in between the selection instead of randomly omitting a few


GitKraken 3.4.1 (32-bit)
- 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


GitKraken 3.4.0 (32-bit)

Features:
- From the depths, a magical window has opened! GitKraken now integrates with Visual Studio Team Services (VSTS)! GitKraken Pro feature - Upgrade now to access!

Improvements:
- 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

Enterprise:
- Beta Feature: GitKraken Enterprise can now be configured to use LDAP as an alternative authentication method


GitKraken 3.3.4 (32-bit)
Features:
- You might see a shiny new menu button. Only click it if you're ready to Glo!

Improvements:
- When discarding a single file through the context menu, you’ll now see a confirmation prompt: also known as the ohnoididntmeantoclickthat prompt


GitKraken 3.3.3 (32-bit)
Features:
- 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.

Improvements:
- 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


GitKraken 3.3.2 (32-bit)

Bug Fixes :
- Users running Git hooks on OSX High Sierra may now commit. We've figured out our commitment issues

Enterprise:
- v3.3.2 does not include any changes to GitKraken Enterprise other than those listed above


GitKraken 3.3.1 (32-bit)
Features:
- Lost in a holidaze of commits? There's now a Fuzzy Finder shortcut to view working directory changes

Improvements:
- 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 EnterpriseSorry not sorry

Bug Fixes:
- 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.

Notes:
- Remotes on GitLab self-hosted accounts will now display the GitLab icon instead of the associated remote avatarTrust us, it's better this way.

Enterprise:
- v3.3.1 does not include any changes to GitKraken Enterprise other than those listed above


GitKraken 3.3.0 (32-bit)
Features:
- GitKraken now integrates with GitLab Community Edition and Enterprise Edition (Pro users only).

Improvements:
- 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


GitKraken 3.2.2 (32-bit)
Features:
- Got GitLab.com? Now you may create a pull request and add a remote from GitKraken

Improvements:
- 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

Enterprise:
- v3.2.2 does not include any changes to GitKraken Enterprise other than those listed above



GitKraken 3.2.1 (32-bit)
Bug Fix:
- Fixed a bug in analytics that caused certain clients to over-report analytics data


GitKraken 3.2.0 (32-bit)
Features:
- 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!

Improvements:
- 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

Bug Fixes:
- GitKraken no longer displays a Pushed Successfully message 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 .gitignore file

Enterprise:
- v3.2 does not include any changes to GitKraken Enterprise other than those listed above