What's New in SmartGit 7.1
Support for HiDPI-Screens, e.g. 4k-Monitors
Instead of blurred or tiny fonts and images you now get a crisp display when using a HiDPI-screen like a 4k-monitor.
When committing files, you may select open issues from Atlassian's JIRA and use it as commit message. When pushing commits, SmartGit will determine affected commits and offer to resolve them for a certain version in JIRA.
Support for Git-LFS
The status of GIT-LFS-managed files is showing up correctly now, completing the GIT-LFS integration (GIT-LFS commands were already working prior to version 7.1).
GitHub and BitBucket OAuth support
For GitHub and BitBucket, the OAuth web flow has been implemented: you won't have to give your passwords to SmartGit anymore but instead use access tokens which have a tailored set of permissions.
The GitHub repository credentials management has been simplified and based upon these access tokens, too.
Detection of Problematic Submodule Configurations
If your submodules are configured to use absolute paths, it might be tricky to rename or move the repository to a new location. SmartGit can detect and fix this by changing the absolute to relative paths.
Change Order of Sync Command
Often requested, now built-in: starting with SmartGit 7.1 you can define whether Sync should first push, then pull or first pull, then push.
Simplified Repository Group Organization
You can organize repositories in groups since a couple of SmartGit versions. Usage is now more intuitive - right-click the repositories and select the target group (or create a new one).
Convenient Registration of Subscription Licenses
Up to SmartGit 7 is was necessary, when registering SmartGit, to always use the latest subscription license file. Now it's also possible to register an outdated license file of an uncancelled subscription and have SmartGit automatically fetch the latest file.
For a complete list of all changes, please refer to the Change Log.
What's New in SmartGit 7
BitBucket and Atlassian Stash
BitBucket and Atlassian Stash are now supported with pull requests and comments, similar to GitHub.
GitLab Hosting Provider
Easily clone your GitLab repositories. You may use your gitlab.com account or your private GitLab installation.
Outgoing: Move and Squash
To amend not the latest commit, but a previous, unpushed one, create a new commit with the name and then drag-and-drop the new commit onto the commit to amend.
The Changes view now shows an information why SmartGit considers a file as binary. It's also possible to force the display as text.
The Mercurial integration has been rewritten to make use of the command server API, making operations more robust and faster.
Bookmark and Better Closed Branch Support
SmartGit 7 lets you create, delete, move and push bookmarks.
The Branches view shows bookmarks in a separate category with their containing branch behind. Closed branches are available in a separate category, too. Unpushed commits (those in draft state) are used to indicate outgoing commit count.
Show Changes to Compare 2 Files
If you have two files selected and invoke Show Changes, you now have the ability to compare the files with each other (as already for Git).
What's New in SmartGit 6.5
External Tools are more powerful
External Tools can be configured to work on commits. Such tools will be available, both in the Branches view and in the Log Graph. There are new variables available to ask for a file or directory name and a customizable confirmation dialog can be optionally displayed before invoking a tool.
Log file/content filters
The Log provides two new filters: searching for touched file names and searching for modified file content in a commit. The responsiveness during filter execution has been improved.
Auto-update across major versions
SmartGit's auto-update mechanism now provides updating the installation source. This will allow you to easily upgrade to new major versions without requiring a new installation. You can also configure to keep your current installation up-to-date in the Preferences.
The Mercurial part of SmartGit now provides the backout command. This allows to "reverse-cherry-pick" commits.
Create/Apply Patch and other tools
Git format-patch and apply-patch have been added as external tool. Fast-Forward Merge allows you to quickly set a tracking branch to its tracked branch. Merge Directly To is a handy tool from Ram Rachum to quickly push changes to a branch, without checking out.
What's New in SmartGit 6
Completely Reworked Repository Management
SmartGit 6 simplifies the repository management by getting rid of "projects" and just knows about repositories. A repository has a name, can be marked as favorite and can be arranged in top-level groups. Each group is sorted by the repository or group names: favorite repositories before groups before non-favorite repositories.
SmartGit shows information about local changes, pushable commits (outgoing changes) and mergable commits (incoming changes) - even for closed repositories.
With drag-and-drop repositories quickly can be added or moved to other groups (by dropping on a group directly or a repository in the target group).
A double-click opens the repository (closing the previously opened one). To open all repositories in a group, right-click the group and select Open. To open multiple repositories, select them, right-click and select Open. To open a repository in a separate window, right-click and select Open in New Window. When closing SmartGit while repositories are open, these repositories will be reopened upon restart. Opening a new window either reopens the open repositories from a previously closed window or shows a list of recently-used repositories.
Common commands like Pull (Fetch), Log or external tools can be invoked on closed repositories. Log also works on bare repositories.
On the first start, common locations are scanned automatically for existing repositories. Additionally, specified directories can be searched recursively for existing repositories.
Background Fetch and Local Change Detection
Favorite repositories can be automatically scanned in background (when idle) for local changes, quickly polled for remote changes, or remote changes can be fetched. This way you quickly get notified about which repository became modified locally or remotely.
Distributed Reviews and the GitHub integration provide support for markdown syntax (e.g. bold, italic styling, bullet lists).
The standard Git-Flow model may be too heavyweight and inflexible for some projects. SmartGit 6 supports a light-weight Git-Flow which only makes use of feature branches.
Improved Submodule Handling
The Files view now also shows submodules, so it's not necessary anymore to resort to the Directories tree to invoke submodule operations. Still, submodules also show up in the Directories tree what helps to avoid the question whether an invoked operation should work on the submodule gitlink of the parent repository or on the submodule repository itself.
Improved Compare Behavior
The navigation to previous or next changes has been improved to show as much as possible from the changed blocks.
Trailing whitespaces and changes in whitespaces can be highlighted optionally. The current line can be highlighted in a different background color, optionally as well.
What's New in SmartGit 5
GitHub: Pull Requests and Comments
If you are using GitHub or have an own GitHub Enterprise instance, you can use Pull Requests and Comments features from inside SmartGit. Instead of leaving the responsibility to merge fixes or new features to all developers, they can send a Pull Request to the system integrator. The system integrator then will fetch the pull request commits, review them and either merge or reject the pull request.
The Comments feature comes in handy, because it allows to add comments to lines of committed files, e.g. as feed-back to a pull request.
SmartGit now supports 2-factor authentication to connect to the GitHub server and relies on API tokens instead of passwords. This improves security, because you have to share the GitHub account password with SmartGit only once, or you can even manually generate the token from the web-fronted. GitHub Enterprise instances are well-supported now and you can have multiple accounts, for github.com and for Enterprise instances at the same time.
In contrast to SVN Git is lacking a standardized way to define how to detect issues in commit messages and convert them to links to your issue tracker. SmartGit goes ahead and supports configurations similar to SVN's bugtraq:* properties. More information you can find at github.com/mstrap/bugtraq.
The Log now allows to pull and push. To visually distinguish unpushed commits, they are shown with orange color and are connected to their parents with thin lines. Tracking branches show how much commits they are ahead (develop 2>) or behind (develop <4) their tracked branch.
Several commands — e.g. to move the head (checkout), reset current branch, move arbitrary refs, cherry-pick or rebase a commit range — now can be performed with drag-and-drop.
For repositories with multiple remotes one now can select on what remote Git-Flow should operate (gitflow.origin).
For those who want to write perfect Git commit messages, SmartGit now optionally shows line length guides at 50/72 characters.
Different files might require different merge tools (e.g. for text or special binary files). As for file comparators, SmartGit now allows to configure different Conflict Solvers depending on the file name.
Sometimes it makes sense to ignore modified, but versioned files. Git allows to mark files with the assume-unchanged flag. SmartGit allows to toggle this flag and you can choose whether to show or hide these files.
What's New in SmartGit 4.6
Git-Flow is a high-level command set wrapping low-level Git commands to support a successful branching model. For the user it significantly reduces the necessary workflow steps and hence reduces the risk of incorrect command usage by less-experienced users.
SmartGit supports an own URI: smartgit://cloneRepo/<URL>. This allows web applications like gitblit.org to easily trigger a clone in SmartGit.
Safe Forced Push
To reducing the risk of overwriting changes using a forced-push, a safety check is performed ensuring that the local 'remote' branch is identical with the one in the remote repository. In other words: the forced-push is rejected if someone else has pushed something to the same branch. You have to perform a fetch first (and get the other user's changes) to successfully perform a forced-push.
What's New in SmartGit 4.5
Syntax Coloring and Quick Line Staging
The built-in file editors (Compare, Conflict Solver and Index Editor) now support syntax coloring based on the file name. The colors and the filename-to-language mappings can be configured in the preferences.
SmartGit 4.5 makes staging (unstaging) hunks or inner-line changes even simpler and directly available in the Changes tool window.
Stash on Demand
The Pull dialog now has a separate button to fetch only (without merging or rebasing).
What's New in SmartGit 4
Improved Mercurial Support
Support for following feature has been added: bookmarks, cherry-pick, rebase, phases and strip.
If you need credentials for accessing your http(s) repository, SmartGit can remember them for you.
Major commands have been added to the Log to execute them directly from there. The Log now also shows the history of renamed or moved files.
Branch-, Stash-, Remote-Handling Simplified
Full SVN-Property Support
SmartGit 4 provides full SVN-property support, so you can merge easily all changes. If you have cloned the SVN repository using a previous SmartGit version, you will see following warning:
Move to Trash
When deleting files, you now can delete to the trash.