Shallow repos are extremely useful when working with huge repositories with long histories and large amounts of data (like binaries).

Since git 1.9 (with better support since 2.5), git has fully supported shallow repos (you can push/pull to/from the remote, etc), and is now very configurable. This lets developers pull down only a small amount of the history, making it faster to work locally (due to less data in the repo that needs to be maintained), and also avoiding the need to pull huge amounts of data over the network when cloning.

SmartGit currently has an option, when cloning a repo, to clone only to a specific depth. However, this is not sufficient for fully supporting a 'shallow repo' workflow, for the following reasons:

Missing functionality:

• If you wish to clone to a specific depth, you only have the option of doing so if you un-check the "fetch all heads and tags". There is no support for fetching all heads so long as they are within the desired commit depth (the "--no-single-branch" option in 'git clone').
• No support for choosing --shallow-submodules vs --no-shallow-submodules when cloning.
• There's only an option to clone to a depth, and not "clone since date" (the "--shallow-since=<date>" option in git clone/fetch)
• No support for --shallow-exclude in clone/fetch/pull
• No way to change the desired depth after cloning (that I could find), to use subsequent fetches/pulls to trim or fill-in the history
• No support for --unshallow, --update-shallow, or --deepen-shallow when fetching

Bugs (as of SmartGit 17.1 preview 6 #11041):

• Regardless of what depth you clone to, when SmartGit does a subsequent fetch, it does not specific the desired depth, so you end up pulling the entire repo anyhow. This defeats the purpose of a shallow clone

This request is similar to https://smartgit.userecho.com/topics/395-implement-a-light-version-of-repository-management/ but expands upon it significantly.

gitflow's last update was about 4 and a half years ago. It's no longer maintained so no new features and more importantly no bug fixes. gitflow-avh is the most popular fork of gitflow and remains active to this day. According to the author of gitflow-avh both Debian and Ubuntu have switched to his fork to provide the git-flow package which is a very good indicator that the original project has died and that AVH is a suitable alternative.

Investigating history of commits with many merges can be a real pain. One useful feature is to be able to locate merge base. Not only for merge commits (though it would be useful on its own), but also for arbitrary pair of commits.

On browsers (well, atleast in chrome), if you have a really wide webpage (Trello for example) You can use Shift+Scroll to scroll wideways rather than up and down.

It would be nice if I could do this on Compare Panel too. For comparing long lines of code.

Not normally a problem, but I have a monitor in portrait orientation, and if you are using Index Editor, it doesn't leave much room. I just noticed it was missing was all.

Please allow paid versions to ignore all synteo messages (help us to improve ..., a new beta versions..., etc.).

For a fresh new SmartGit install in my team, we always need to change the default pull behavior : doing a rebase with local changes instead of a merge commit. The later produces absolutely unreadable logs and I think for the vast majority of users is an aberration.

So I'd suggest to change the default value, or make it configurable as soon as clogin / opening a new repo.

SmartGit should support git-repo. https://code.google.com/p/git-repo/

This is a multiple repository management tool built by google used by several large fortune 500 companies. It provides a easy way to sync a large number of repos (over 100 or more) to a specified commit tag that is specified in a manifest file, which is in it's own repo. This is how we are managing our software build where each project can contain hundreds of repos.

It's already in the "Show Changes" option, but you should add a setting to use that editor when you double click on a file in the files tab.

Currently the new repository is appended to the bottom of the list, it would be nice if it's added to the currently selected repository group instead (or add the "repository group" select box to the "Add repository..." dialog and make the currently selected group the default option). It's tedious to have to scroll and drag the new repo through the long list.

However, "after" executing a command from SmartGit is showed in the Output window but showing the respective git command will make CLI users easily aware of the commands provided by SmartGit "before" actually executing; and newbies can also learn commands.