Git kraken mac os

How to Install GitKraken Git GUI

There are three steps to success with GitKraken. That’s it!

No Git tools are required for GitKraken, so once you’ve run the installer, you can open the app and get going.

It works directly with your repositories with no dependencies—you don’t even need to have Git installed on your system. GitKraken is built with NodeGit, a Git framework that is primarily developed and maintained by members of the GitKraken development team.

Below are platform-specific details on minimum requirements.

Looking for GitKraken Enterprise installation instructions? Then please start in with our Enterprise System Requirements page.

Windows (.exe file)

• System requirements: Windows 10
• Download (64-bit)
• Download (32-bit)

Install Instructions

Double-click the downloaded executable file, and follow the installation instructions.

Data Location

GitKraken data is stored with your home profile in C:\Users\\AppData\Roaming in the .gitkraken folder.

Mac OS (.dmg file)

• System requirements: Mac OS X 10.9+ (up to and including OS X El Capitan) / macOS Sierra or later
• Download

Install Instructions

Double click the downloaded DMG file and when prompted, drag and drop the GitKraken icon to your Applications folder.

Data Location

GitKraken data is stored in /Users//.gitkraken ==

Linux (.deb, .rpm, and .tar.gz files)

• .deb system requirements: Ubuntu 16.04 LTS or later
• .rpm system requirements: RHEL 7+, CentOS 7+, or Fedora 33+

Note рџ“ќ — GitKraken currently supports Ubuntu 16.04 LTS+, RHEL 7+, CentOS 7+, and Fedora 33+. While GitKraken may be able to be installed on other Linux distributions, we cannot guarantee that it will work as expected.

GitKraken has a simple package available for Debian based distributions.

Snap is an easy-to-install package for Linux distributions (supported versions above). Get it from the snap store or Snapcraft.io.

Data Location

GitKraken data is stored in /home//.gitkraken ==

Run GitKraken

Upon installation, some Linux distros do not automatically create shortcuts to the app.

To run GitKraken manually, open the terminal and type gitkraken to start the app.

Источник

Stand-Alone

GitKraken Stand-Alone is built for teams of 10+ who work in a disconnected development environment. You get all the same core GitKraken features, along with these additional benefits:

• For use without internet
• No account creation required
• No server installation

Looking to get started with GitKraken Stand-Alone? Email sales@gitkraken.com for a free trial key.

How to install GitKraken Stand-Alone

There are 3 steps to installing GitKraken Stand-Alone:

1. Download GitKraken Stand-Alone
2. Install GitKraken
3. Load .dat license file

1. Download GitKraken Stand-Alone

The GitKraken Stand-Alone clients are available on our downloads page.

If you are unable to access this page, please contact your GitKraken administrator for Stand-Alone client downloads. There is a high probability they have made the files available in a different, internal location.

2. Install GitKraken Stand-Alone

Once you download the client, double click the file to install GitKraken Stand-Alone on your machine.

Below are platform-specific details on minimum requirements.

Windows (.exe file)

• System requirements: Windows 10

Install Instructions

Double-click the downloaded executable file, and follow the installation instructions.

Data Location

GitKraken data is stored within your home profile in C:\Users\\AppData\Roaming or %APPDATA%/.gitkraken on older versions. No data is stored outside of the user’s machine or remote services (GitHub Enterprise, Bitbucket Server, etc).

Mac OS (.dmg file)

• System requirements: Mac OS X 10.9+ (up to and including OS X El Capitan) / macOS Sierra or later

Install Instructions

Double click the downloaded DMG file and when prompted, drag and drop the GitKraken icon to your Applications folder.

Data Location

GitKraken data is stored in /Users//.gitkraken ==

/.gitkraken . No data is stored outside of user’s machine or remote services (GitHub Enterprise, Bitbucket Server, etc).

Linux (.deb and .tar.gz files)

• System requirements: Ubuntu LTS 16.04 or later

GitKraken has a simple package available for Debian based distributions.

Data Location

GitKraken data is stored in /home//.gitkraken ==

/.gitkraken . No data is stored outside of user’s machine or remote services (GitHub Enterprise, Bitbucket Server, etc).

3. Load license file

When you first open GitKraken Stand-Alone, you will be prompted to load the .dat license file.

If do not have the license, please contact your GitKraken administrator. If you are the GitKraken administrator, please contact sales@gitkraken.com for the license file associated with your purchase.

Once the license file is applied, you are ready to get crackin’!

License.dat Location

You can also place your license file directly into certain directory locations for GitKraken to check. Here are all of the locations GitKraken will look:

Источник

GitKraken Git GUI 8.x

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.

Check out our GitKraken Roadmap to see what we’re working on.

Version 8.0.1

Tuesday, September 28th, 2021

Everyone: “I am loving v8.”
GitKraken: “Let’s make the experience even better!”

Improvements рџ™Њ

• GitKraken users can now search for a particular tab and navigate the menu using the keyboard when using the tab dropdown menu.

Bug Fixes рџђ›

• Gitflow branch folders and tag folders collapse and expand as expected when selected in the left panel in GitKraken.
• Layout and options have been optimized in the Organization panel in GitKraken’s Preference view.

Version 8.0.0

Tuesday, September 21st, 2021

«It began with the forging of the Great Rings Kraken.»

The true power of the Fellowship of developer collaboration is unleashed in GitKraken v8.0!

New вњЁ

“One tool to rule them all,
One tool to find them,
One tool to bring them all
and in the Git log bind them.”

Introducing the GitKraken CLI Preview

The GitKraken CLI adds a Git-enhanced, keyboard-driven, terminal experience to the GitKraken Git Client. Get the powerful Git visualizations GitKraken is known for—like the commit graph—in the context of a Terminal Tab. Plus auto-suggest and auto-complete for Git commands to help you drive (and learn) Git faster, with fewer mistakes.

Dive deeper into file changes with the gk commands. Use the command gk history to see File History and gk blame to see what has changed in a file or commit and who made those changes.

During the GitKraken CLI Preview we are looking for feedback to help improve this feature. Please use the Feedback form linked in the bottom right corner of your GitKraken app, or email us at feedback@gitkraken.com.

Users can open Terminal Tabs in a number of ways:

• Clicking the «New Terminal Tab» button after opening a New tab in GitKraken.
• From the «Terminal» button in the toolbar of a Repo tab (opens the current repo in a Terminal Tab).
• From the Command Palette ( Ctrl/Cmd + P ).
• When working in a Terminal Tab, you can open a new Terminal Tab with the key combination Ctrl/Cmd + T . The new Terminal Tab will open in the same working directory.

Auto-complete and auto-suggest make building Git commands easier than ever before in the GitKraken CLI. This feature works for users of PowerShell for Windows, ZSH and Bash for Mac/Linux.

• Auto-complete and auto-suggest are configured for the most common Git commands, but we are continuing to build out this feature and would love feedback on which commands and parameters you want added.
• Please be aware that other auto-complete programs could potentially cause the GitKraken CLI auto-complete to stop working. You may need to uninstall or disable those other programs to use this feature.
• Note: If you switch shells, you’ll need to set the new shell as default in your operating system settings and restart your computer for auto-complete to continue working as expected.

Some of the legendary Git visualizations that GitKraken is known for are also accessible within Terminal Tabs. To quickly view the commit graph, file diff, history, and blame view, simply type these commands:

• gk panel : toggles the visualization panel on or off. You can also reposition the panel to the top, bottom, left, or right by adding those parameters to the command. For example gk panel right moves the panel to the right of the screen.
• gk graph : shows the graph view. While this command has similar behavior to gk panel , even allowing repositioning of the graph with the same top, bottom, left, or right parameters, this command also returns to the graph if you’re in a different view and has subcommands for toggling the graph columns with the keyboard.
• gk history and gk blame : open the history or blame panel for a specified file.
• gk diff : shows changes between commits. If no commit SHAs are provided, it will use your WIP and HEAD. If only one commit SHA is provided, it will be compared with HEAD.
• gk —help : shows the list of available gk commands. You can also use —help on a specific gk command to see its arguments.
• A toolbar above the panel will display the current repository name, branch, tag, and the number of changes pending to be pulled and/or pushed. Clicking this toolbar will toggle the panel on or off.
• For Free accounts, this visualization panel will only be accessible within publicly-hosted repositories.

A Terminal section has been added to the Preferences menu that allows Terminal Tab customization:

• Font choice. Changes to this setting will only apply to new Terminal Tabs.
• Font size.
• Enable auto-complete & auto-suggest.
• Default the visualization panel position when opening a new panel: top, right, bottom, or left.
• Show the visualization panel by default. This will apply only when opening new tabs.
• Terminal theme.

The GitKraken CLI Preview is currently unavailable for Self-hosted and Stand-alone customers.

Deep Linking

«Oh, it’s quite simple. If you are a friend, you speak the password, click the link, and the doors will open.»

We’ve added the ability to share deep links to specific remote repositories, commits, branches, and tags in GitKraken. This allows users to more easily collaborate and save time when working in issue queues or Git pull requests.

• When shared, these links will both open and focus GitKraken to the linked repository. The links will focus GitKraken on the commit, branch, or tag specified. When specifying a branch, the latest commit of that branch will be focused.
• The links can be found in GitKraken’s context menus under Copy link to remote/commit/branch/tag .

Jira App Integration — Git Integration for Jira

«It’s the Jira ticket that’s never started that takes the longest to finish.»

GitKraken now works with the Git Integration for Jira app to allow quick navigation between GitKraken and Jira when viewing commits and file diffs related to Jira issues.

In GitKraken, you’ll find buttons and links to open the following in Git Integration for Jira:

• File diffs — within the file diff view and in file context menus.
• Commits — context menu when right-clicking commits in the graph.

In the Git Integration for Jira, anywhere you view commits and diffs will automatically have links to open them in GitKraken.

To leverage GitKraken’s Git Integration for Jira integration you will need to:

• Connect Jira Cloud Integration in GitKraken.
• Select Jira Cloud as the Issue Tracker for a repository.
• Select a Jira Project.
• Install Git Integration for Jira on the same Jira Cloud instance as the Jira Project.

Improvements рџ™Њ

«Even the smallest update can change the course of history.»

• The Fuzzy Finder is now the Command Palette!
  • We’ve renamed the Fuzzy Finder to the Command Palette. You can still open the command palette through the keyboard shortcut Ctrl/Cmd + P , or through the new magic wand icon in the toolbar.
• Tab navigation has been significantly improved when many tabs are open at once.
  • We have improved the tooltips to provide both tab title and repo information.
  • Tooltips will now instantly appear when hovering the entire tab, not just the title.
  • A new dropdown list has been added to the tabs bar to help with tab navigation.
• Reopening tabs after a “close all tabs to the right”, a “reopen closed tab” will now reopen only one tab at a time, instead of all that were closed at once.
• An option to “Quote Reply” has been added for comments in the PR view.
• The profile menu now shows the Organization associated with the current profile.
• A “Cancel Rebase” button has been added at the top right of the Interactive Rebase panel for easier access.
• We have improved form, prompt, and modal keyboard navigation and submission.
• Improved user experience for the login form.

Bug Fixes рџђ›

«You (bugs) shall not pass!»

• Styling of long branch names in the right panel has been improved.
• Users will no longer see issues for remotes without access to a repo, as happens when users leave an organization or when forks are deleted.
• When using the delete key to erase spaces in a URL, the cursor will behave as expected.
• The Pull Request icon has been added back to branch labels in the graph.
• The bottom of Diff views are no longer cut off when the file mode changes.
• Relative paths are now allowed in hooksPath.
• All users are now able to select a project for GitLab and GitLab-Self-Managed issues on the left panel.
• If Sublime Text 4 is installed, it will now be detected and appear in the external editor dropdown.
• Debouncing has been added in the left panel search. Searches will be executed when you stop typing, instead of on each letter, making it easier to find what you’re looking for.

Источник