Next Version Preview

What's new in SmartGit 24.1 RC 4?

For SmartGit 24.1, we have mainly focused on optimizing common workflows like setting up hosting providers or cloning a repository.

Standard Window improvements

Switching to a submodule became easier.

Easier Switching to Submodule

For repositories with submodules it became much easier to open such a submodule.

Fix Case-Changed Files

Case-changed files are highlighted and two options are offered to fix it: either rename the working tree file back to the repository case, or rename the file in the repository.

Fix for case-changed files.
Find and edit git ignore files.

Edit Git Ignore File

This feature (which already exists in the Working Tree and Log window) helps in identifying which Git ignore file causes a file to be ignored, or to simply edit one of the multiple Git ignore files.

Subdirectory Log

You also can invoke a subdirectory log to limit the amount of shown commits to those which contain modifications inside this subdirectory.

Invoke the log from a subdirectory.
Easy way to open repository in browser.

Open at Hosting Provider

For repositories of a hosting provider, e.g. GitHub, it became easier to open the commit or repository in the browser.

General improvements

Cloning from Hosting Provider

The Cloning from a Hosting Provider has been significantly improved, making it not just more obvious, but also visually attractive.

For GitHub, you can specify which repositories will be listed (e.g. own or starred repositories). Organizations that are inaccessible via OAuth no longer disrupt the listing process; instead, a warning will be shown. Additionally, query performance has been significantly improved.

Cloning from a hosting provider has been simplified.
When cloning, the active branch is not preselected.

Clone: Active Branch

The administrator of a repository can configure which is the active (main) branch of a repository. SmartGit now preselects this branch for cloning.

Clone: easier directory selection

If you store your repositories in multiple topic-specific directories, the improved directory selection makes it easier to select the location and/or change the name of the directory.

Easier selection for the directory when cloning.
Allows to select an issue from GitHub.

Select Issue from GitHub

Like for the JIRA integration you now can select a ticket from GitHub for a commit message.

Work with Multiple Accounts at same Hosting Provider

When having multiple accounts at one hosting provider, such as GitHub, SmartGit allows you to select which account to use. This choice is remembered as URL-to-account mapping and will be automatically applied to new clones.

Select which hosting provider account to use.
The log optionally can follow copies.

File Log, Blame, Investigate: Follow copies

Sometimes, added files are not created from scratch but are instead modifications of existing files. The File Log, Blame, and Investigate commands can now optionally detect these copies and proceed with the operation for these copy-sources.

Changes view: Ignore Irrelevant Whitespace

Sometimes, e.g. after a source code file has been reformatted, it is helpful to ignore irrelevant whitespaces. Together with the new syntax-based coloring, the new toolbar button quickly allows to hide all whitespace changes that don't change the meaning of the code.

To avoid accidentally committing unnoticed whitespace changes, this option is automatically reset for local files if the selection is changed. For viewing committed files, it is preserved.

Optionally, irrelevant whitespace can be ignored for the diff.
Rollback sets the working tree or index to the state of the selected commit.

Rollback-To

Rollback-To is a new power-user command that will set the working tree or index to the state of the selected commit. It can be executed on an entire commit (affecting all files) or on specific files within a commit.

This feature is very helpful for rebuilding a small feature branch where the last commit should contain all the remaining changes of the previous feature branch.

SmartGit can be used as credential helper for Git command line.

SmartGit as Credential Helper

When cloning a repository using SmartGit, it can optionally configure the repository so that when using the command line for Git commands, SmartGit will handle authentication.

This can be very helpful if you primarily use SmartGit but also need to run scripts for your company's specific workflows. By doing so, you can ensure that your credentials are stored in one central location.

Add Upstream Remote

If you've cloned your fork of a GitHub repository without creating the upstream remote, you can add that later just by invoking Remote | Add. The input fields will be prefilled with the upstream data.

Easy adding of upstream remote.
Easier selection of the bundled Git.

Easier selection of bundled Git

It is now easier to select the bundled Git or another Git executable.

The detected Git and Git-LFS versions are shown.

Compare: better selection color

The selection color is now kept even if the control actually is not focused (which happened for showing a Find dialog or a context menu).

The background color of the selection is better noticable.
The controls are now correctly aligned on MacOS, too.

Fixed Control Alignment on Mac OS

On Mac OS the controls, especially labels, checkboxes and radio buttons, were vertically not aligned on the font's base line. This has been fixed now.

Stream-Lined Setup

The setup of SmartGit has been stream-lined by removing non-essential parts (the SSH client can be configured in the preferences, anyway) and reordering the pages.

The Setup process has been stream-lined.
The hosting provider configuration has been simplified.

Split Cloud/Enterprise Hosting Providers

The Hosting Providers have been split into cloud and enterprise which simplified the configurations.

Download SmartGit 24.1 RC 4

Usually, SmartGit preview versions are quite reliable (we use them on a daily basis).
However - as it is the case with other previews - they may have problems. Should you encounter such a problem, please report it to the development-team.
You can safely use a preview version side-by-side with the release version.
Download for Windows
Windows 10+ (64-bit), Installer  
Size: 134,508,832 Bytes
SHA-1: 749b847fbd683410e637f6417944a1b034f8fd8f
Portable Bundle
Windows 10+ (64-bit), Archive (7z)  
Size: 114,667,144 Bytes
SHA-1: 0f994319056e02d06f4dddd042a4f8253cea3825
Download for macOS
macOS 10.14 - 15, Archive (dmg)  
Size: 88,193,841 Bytes
SHA-1: d9b3fb40f602fb6e1a3a612da4672e08eaf48ff1
Bundle for ARM64
macOS 11 - 15, Archive (dmg)  
Size: 87,336,599 Bytes
SHA-1: b21f0a3e4f665154ff0f75b4d6b7be6441fc8cf4
Download for Linux
Linux (64-bit, GTK 3.24+), Archive (tar.gz)  
Size: 114,210,650 Bytes
SHA-1: cb1bf4d51fd232aece812599b7c96f32423324b4
Debian Bundle (not recommended)
Linux (64-bit, GTK 3.24+), Archive (deb)  
Size: 57,022,012 Bytes
SHA-1: 3bfaad884c47996425b8362bcad70d6a3ac9c673

Note

This preview version is a "rolling" release so it will require direct internet access to download the latest patches.

You can install and use the preview version in parallel to the release version, in this case:

  • For Windows, make sure to use the Portable bundle. The installer won't work for such a setup.
  • The preview version (except of the portable Windows bundle) will initially copy the settings from the release version, but writes them to its own settings directory. This means that settings of both versions will diverge.