Share your ideas on how to improve SmartGit!


This is no support platform! To report bugs or request support, please contact us directly. If in doubt ask us.


First search for a similar request and add your votes or comments there.


Take the time to describe your request as precise as possible, so users will understand what you want.


Follow the stackoverflow.com writing guidelines.

Thank you for your help!

+2

Commit authoring: support for GitHub's "Co-Authored-By"

Pierre Goiffon 5 years ago updated by Marc Strapetz 5 years ago 5

When merging a pull request in GitHub, both the PR creator and the committer appears in the new commit ("By" = PR creator, and "committed by" = the one that merged the PR)

It happens that I need to commit something that was made by another developer, so I would love to be able to do exactly the same : set the "By" to the real author of the code, and my name only appearing as the committer.

Also, when working in pair, it would be nice to be able to add the other developer as author...

Would be perfect to be able to pick the name/email from the log (people that did already commit).

May the "Co-Authored-By" be useful for this ?

+2

Log: filter should (optionally) not hide but gray unmatched commits (SG-12145)

zuber 5 years ago updated by Marc Strapetz 5 years ago 4

E.g. to have all commits from a specific user highlighted.

+2

Different icons for «Log Graph» & «Working Tree»

arcadius 5 years ago updated 5 years ago 2

When both windows are open, it's hard to distinguish one from the other, f.e. when switching between them by Alt+Tab:

Image 330

It would be convenient if, f.e., one of windows icons were painted with some color:

Image 331

+2

GitHub: view all pull requests for all repositories

rsignup 5 years ago updated by Marc Strapetz 5 years ago 0

Hi,

I would like to see a view that would list all PR's from all repositories that SmartGit knows of, very useful when your working in projects with many repos and many PR's to review

+2

Goto/Jump/Cycle through open repositories

quincunx 5 years ago 0

When groups are collapsed, there is no easy way to find an open repository (specially if one is using nested groups; see https://smartgit.userecho.com/communities/1/topics/291-highlight-group-name-of-opened-repository, too).

It would be great to have either (or all :-)) of:

* A function (menu entry, toolbar button, keyboard shortcut) to jump to the next open repository (invoking the action multiple times would cycle through open repositories)

* A list of open repositories in the window-menu

* Integration into "Find Object", e.g. either list open repos first or use a special command like "open" to list open repositories

+2

Log, Commits: "Working Tree (3 changes)" --> "Working Tree (1 change, 2 untracked)"

Wolfgang Gauch 5 years ago updated by Marc Strapetz 5 years ago 0

git status lists "modified" files separate from "untracked", and does this for a reason.

SmartGit seems to add these two counts to one "changed" count.

When I committed all my modified files, I often have some untracked files (i have good reasons not to ignore or stash them), which always makes me think: did I forgot to commit something or are they just the untracked? and I need to check the files list.

If SmartGit would count them separate as git status does, that would save the hassle.

+2

merge --ours without conflicts

Mario123 5 years ago updated 5 years ago 1

When working with several active release we usually develop the feature in the oldest active release and the merge things upwards to newer versions. 

For this usecase we need an option to ignore the whole merge in newer releases if it's not needed in here. Git provides this via `git merge --ours `

+2

Commit-hook: parse for warnings case insensitive

marcelpetrick 5 years ago updated by Thomas Singer 5 years ago 0

Please change the behaviour of the parsing of the results of the (pre-)commit hooks for SmartGit. One of our scripts echoes a "WARNING:" instead of the currently accepted  "warning:" as prefix. Therefore that warning is not reflected properly in the SmartGit-UI while committing. Please make the parsing case-insensitive.

+2
Completed

Log, Commits view: provide "Commit" action when right clicking on working tree item (context menu)

Klaus0x07C4 5 years ago updated by Thomas Singer 5 years ago 1

Image 301

It would be nice to have the "Commit" action in the context menu of the "Working Tree" item in the log view (version 18.2.+).

+2

Allow the "Find Object" window to match submodules from a open repository

Bugged 5 years ago 0

Currently, while using the Working Tree Window, if I have a repository with several submodules, and I hit to open the "Find Object" dialog, it only show the side bar repositories, but does not show any submodules from the opened repositories for selection.