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 precisely as possible, so users will understand what you want. Please note that we appreciate your time and input, but we don't give any guarantees that a certain feature will be implemented. Usually, a minimum requirement is a sufficient number of votes. Hence, please don't comment like "when will this be implemented", but vote instead.

Follow the stackoverflow.com writing guidelines.

Thank you for your help!

+2

Integrate "Merge directly to" tool into SmartGit

Mikhail Matrosov 6 years ago 0

There is a very useful tool "Merge directly to" present in SmartGit for years. I used to use it in some older versions, but then at some point it stopped working. I find it very convenient, since it allows me to preserve timestamps of my files on merge and thus avoid recompilation of the code (I work with C++ code base). Please recover the tool.

+2

Option to open reviewed file in editor (on selected line)

Jan Ryšavý 6 years ago updated by David Rees 3 years ago 3

It would be great to have an option to open reviewed file in selected text editor.


For example I find some typo like missing space:

Image 387


I would like to open file in my text editor (in my case VS2019) on highlighted line.


Just for reference I'm attaching code for opening VS on selected line. It would mean support also VS Code and other major text editors (maybe some configuration and external commands?)

openedit.cpp

+2

Branches view: ahead/behind commits should not include merge commits (pre-19.1 counting)

Kevin Hoang 6 years ago updated by Marc Strapetz 6 years ago 0

Since version 19.1 the way of the ahead/behind commit counting has been changed (it counts both current branch and merge branch commits). It makes us confuse about: how many commits had been reset on a branch or how many ahead commits of the current branch. So I think best would be to have an option/setting to switch back to pre-19.1 counting.

+2

Add support for actions on Nested groups in Repositories View

Chris Jaquet 6 years ago updated by Marc Strapetz 6 years ago 3

I recently discovered that you can nest groups in the Repositories view. This is an incredibly useful feature for us (as we work with over 100 repositories at a time).

I have a structure similar to the following:

ApplicationSuite (Group)
  + Apps (Group)
      + Repo One
      + Repo Two
  + Libraries (Group)
      + Repo Three
      + Repo Four
  + DataSets (Group)
      + Set One (Group)
          + Repo Five
          + Repo Six
      + Set Two (Group)
          + Repo Seven
          + Repo Eight
   + Repo Nine


The following enhancements (wishlist items) would make our lives even easier:

  1. If you right-click on the parent group (e.g. ApplicationSuite) and choose "Open Repository", it should open all repositories in that group (Repo Nine) as well as all child groups (Apps, Libraries, etc) all the way down the tree. At the moment you need to expand all the groups you want to open the repositories for, select all the repos and the right click and choose "Open Repository"
  2. Add the ability to see changed files in the current group as well as any sub groups. This would probably need to be an optional mode (controlled with (for example) a button next to the file filter text box) so that the current behaviour of only showing repos in the current group is still available. The behaviour and available options for the "expanded/recursive" mode would be the same as for a single selected group (being able to commit, stage, etc.).
    +2

    Gitea / Gogs

    Chriztoffer 6 years ago 0
    Have it been considered to review basic support of Gitea / Gogs,too. Now that GitLab support has crept into SmartGit, along with the big-brother of them all. GitHub.

    +2
    Completed

    Add menu to completely remove a worktree

    Iulian Onofrei 6 years ago updated by Endolith 5 years ago 10
    +2

    SmartSynchronize: Mark files for comparison from explorer context menu

    Mario123 6 years ago in SmartSynchronize updated by Michael 6 years ago 4

    Unlike ExamDiff there seems to be no possibility to mark files for comparison from the context menu of windows explorer. That would be a great extension.

    Use case:

    Select one file in windows explorer, use right click to open the context menu and then click on "Add to Comparison".

    After that add another file to comparison using the context menu and select "Compare against xyz.ztx"

    +2

    Log, Details: show "On Tags" similar to "On Branches"

    pgoiffon 6 years ago updated by Thomas Singer 6 years ago 0

    When doing support on a product, you're quite often confront to questions like "in which version does this fix/enhancement is integrated ?". When you got he sha, the "git tag --contains <sha>" command gives a good answer.

    I added this as a new tool, but I think this could be useful to others, so maybe integrate this directly in Smartgit ?

    +2

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

    pgoiffon 6 years ago updated by Marc Strapetz 6 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 6 years ago updated by Marc Strapetz 6 years ago 4

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