Currently, the Github integration for enterprise instances in SmartGit uses the same proxy settings as the main application proxy settings. However, there is a fundamental difference that should be allowed for- an enterprise instance probably is not being connected to via the internet, and thus the proxy settings of the main application prevent connectivity to the enterprise github. In my particular case, the enterprise github actually does require a proxy, but not the same proxy as an internet connection.

dirs like

/home/user/workspace

- work1

  - proj1

  - proj12

- work2

  - proj1

- github

  - ...

- demo

- ...

on import to smart git should create corresponding groups in repositories view 

It would be nice if you could view the index of the currently highlighted change along the previous and next change buttons like "23/56".

Please add support for Swift syntax highlighting.

GitFlow currently can't be set to default to major.minor.patch release formats.

Every time I start a new release it auto-bumps minor despite the most
recent release branch being in major.minor.patch format (i.e. 4.7.11 ,
start release creates 4.8 not 4.7.12).

My understanding is that some other GitFlow products support the 3-level release format and fall back to major.minor.

Does anyone know if the system level gitflow for MacOS supports the 3-level release format?

Not just MySpell dictionaries.

Just like for branches, need to see what tags exist for a certain branch, so you can add a new one before/after some changes in that branch.

While refactoring some code, I often have to split up large files into smaller ones. This results in loosing the history of all code which is relocated from the original file.

As a countermeasure I found this workaround for git:

- first duplicate the original file (copy it using a new filename and/or location)

- commit this duplication without any changes (this is a commit which might not build properly)

- remove the duplicate code from both files

- commit changes (this commit should work fine)

On the commandline, using "git log --follow" it is now possible to track all changes of the new file across the duplication step. With smartgit this does not work; smartgit seems to follow renamed files only.

I would like to propose a (maybe optional) follow-copy-strategy in the log view - from my point of view only exact copies need to be detected, which should keep the cost at minimum.

E.g. if any branch heads to any commit included in the branch currently checked out, show it's label instead of showing just the branch currently checked out local and remote labels.

It is extremely common that one starts a feature or bug prior to actually starting the GitFlow process. This means there are often unstaged changes before starting a GitFlow bug/feature. When you do this, it will fail as there are uncommitted changes when it needs to change branch/make a branch/etc.

Unfortunately SmartGit isn't automatically stashing/unstashing in response to this. Which makes using GitFlwo very frustrating.

It should be no issue to stash all changes, perform the GitFlow process, then unstash.