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!

+4

"Creature Comfort" enhancements for Groups

warholscribe 5 years ago updated by anonymous 5 years ago 1

Long time SmartGit user!


I've been using SmartGit exclusively for almost 10 years now, and over the course of time have accumulated access to almost 70 distinct source repositories related to/necessary for my job functions.  As a result, I'm heavily dependent upon the functionality that's provided by Repository Groups.


It would be helpful/useful to expand upon the attribute set currently afforded by Repository Groups, to include the following:


1. The ability to optionally specify (and edit) a short description or comment for the group.  This description could then appear upon hover over the group in the Repositories view.  (some of the "legacy" repositories and parent groups I maintain are used infrequently, and a tool tip that additionally helps to identify the purpose/intent of the Repository Group - and its subordinate repositories - would be helpful).

2. The ability to optionally specify (and edit) a color for the group, which affects the either the folder icon and/or text color of the group name displayed in the Repositories view.  (some of the "legacy" repository and parent Repository Groups I maintain are used infrequently, and a identifiable color that helps better distinguish Repository Groups from one another would be helpful).

+4

LFS: lock multiple files

Andreas75 5 years ago updated by Code Weaver 6 months ago 9

LFS->Lock seems only to work with the currently selected file. Selecting multiple files will disable this options in the context menu. For my work it would be great if it would also work for selected files (maybe with an additional dialogue).

+4

Pull: Automatically decide between merge and rebase (smart pull)

jonathan bogdoll 6 years ago 0

Pull already lets you choose between merge and rebase as well as setting a default action. I propose an additional smart mode mapped to a separate toolbar button, which can be added to the toolbar and/or replace regular pull if desired:

- If there are no local changes...

-- ... and no local commits, fast forward without asking

-- ... and local commits, rebase without asking (optional warning, if there are a lot of incoming commits)

- If there are local changes...

-- ... and no local commits, attempt to pull with merge, on failure offer stash&retry

-- ... and local commits, warn user and offer to stash and proceed with rebase

+4

Log graph: customize color per remote

Michał Sochoń 6 years ago updated by Patrick Lehmann 6 years ago 1

As an user I'd like to be able to define background color label per git remote.

Right now graph window shows remote/branch labels with bright yellow background.

I'd like to adjust background for certain repos to make it more distinct.

+4

Allow choosing the default destination for new ignore rules

Patrick Lehmann 6 years ago updated by Thomas Singer 4 years ago 5

This is a followup / extension to:

    Currently, adding new ignored files will be stored in a local .gitignore file (local to the ignored file / same directory). It would be nice if the default option for the destination dropdown box could be selected in settings.

    Currently, I need to change the dropdown on every ignored file or pattern to .gitignore in the repository root.

    Image 413

    +4

    Allow existing repo actions on selected groups

    Jeff Jensen 6 years ago updated by Marc Strapetz 4 years ago 2

    Currently, the user can select multiple repos and perform the same action on all of them, such as pull. Instead of selecting the individual repos, please allow the same repo actions on the selected groups.

    +4

    GitLab Issue Tracker support

    Mario123 6 years ago updated by Thomas Singer 2 years ago 3

    We're using a self hosted gitlab server instance using the community edition.

    Using the integration with a Gitlab instances only allows us to see all projects granted access to me or seeing and creating merge request.

    Since we're also using the gitlab issue tracker it would be great to add a better integration with the issues, e.g:

    • Show Issue Numbers in log view that relate to commits (next to authors)
    • Create issues prior to commits with a simple dialogue (for minor issues this would be great)
    • Provide additional information during the commit to not only close an issues (gitlab automatically does this if wrting 'fixes #123') but also to label or assign milestones to it.
    +4

    Edit Author command: allow to pick author from list

    pgoiffon 6 years ago updated by Marc Strapetz 6 years ago 0

    This follows this topic : https://smartgit.userecho.com/communities/1/topics/960-github-allow-to-set-author-and-commiter#

    The "edit author" is quite cool, but you need to write manually both author name and email.

    It would be nice to be able to pick name and email directly from a list generated from the log (all authors in the repo would be perfect)

    +4

    Push/Rebase/etc --no-verify checkbox for skipping githooks

    kiramp 6 years ago 0

    Please add --no-verify checkbox to interface or field "custom args". 

    +4

    Remember multiple window instances with positions and opened repositories

    Bugged 6 years ago updated by Chris Jaquet 5 months ago 2

    For example, if you have the Google Chrome setting `Continue where you left off`, enabled:

    Image 309

    And you exit Google Chrome with `File -> Exit`, or you computer just crashes (i.e., abruptly restarts), the next time you open Google Chrome, it restores (i.e., opens back) all opened windows and tabs.

    Currently, if I have 2 Working Tree opened, each one with a different repository and I do `File  -> Exit` with SmartGit, the next time SmartGit reopens, it will open back only one (1) window, with the 2 repositories opened.

    This behavior is not desired because if I had two (2) windows opened, each one with a different repository open, I would like for SmartGit to keep it that way, the next time I open it.

    It also would be nive if SmartGit can:

    1. Restore my two (2) opened windows, in case my computer crashes (i.e., abruptly restarts)
    2. Also restore any Log Window, in case I had one of them opened.
    GUI