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!

0

Standard Window + simple Workflow: Locking Support, "open file dialogue" and stash Capability

Sascha P 3 years ago 0

Hi guys!

Wanted to congratulate You on the simplified views for 22.1!

As someone who is responsible for supporting users of varying git-knowledge, it is greatly appreciated that You are taking steps towards making Git more accessible to the uninitiated. ;)

(I for one would be very glad to get rid of our tertiary, error prone Git GUI, that we use for training purposes primarily, and which has striking resemblance to this new view ;))

Some Remarks from my side:

Our document-engineers needn't concern themselves with advanced git stuff, but would like to see:

* Ability to lock and unlock office files

* Open files from within GUI

* When they realize they forgot to lock, they should have the ability to stash changes before pull

Within standard view + simple workflow, these are not possible currently.

As a bonus, it would be nice for them to see the locking status of documents before attempting to lock.

Currently, You have to configure pull operation to fetch lock status. This is not something that the average user expects.

BR, Sascha

0

Tools should support env-variables in Command

Mario123 3 years ago updated by Thomas Singer 3 years ago 1

Using external tools in Smartgit could be greatly improved for us using templates for new accelerators which accepts system-env vars as command inputs.

e.g.: %LOCALAPPDATA%\Programs\Microsoft VS Code\Code.exe 

as a command value is not being processed by smartgit.

0
Completed

Show progress for Filtering Content during clone [SG-15033]

Alpaka 3 years ago updated by Marc Strapetz 3 years ago 1

When cloning a repository, SmartGit shows a nice progress-bar, except for the step "Filtering content", which is usually quite fast, but in my example, it took several minutes. Not knowing, whether SmartGit hung up or not, I force-closed the application and cloned the repo from the command line.

It would be great to show the progress and that something is still going on while the clone operation is filtering content.

Image 655

instead, the UI gets stuck here for a very long time:

Image 656

Answer
Marc Strapetz 3 years ago

What kind of filter is this? Git-LFS?

0
Declined

Make it possible to add an empty folder to a repository

Markus2021 3 years ago updated 3 years ago 4

Allow to add an empty folder to a repository and put that under version control. This is useful if somebody wants to define a folder structure to be used by some other developer but has no contents yet for these folders as that content shall be generated by the other developer.

0

Rename: allow to move file to not yet existing directories

Markus2021 3 years ago updated by Marc Strapetz 3 years ago 7

Make it possible to move a file already under version control to a newly created subfolder within the working copy which has not yet been added to version control because you do not allow empty folders to get added to version control.

0

Integrate Output Strip for Jupyter

Royi 3 years ago updated 3 years ago 4

Could you integrate something like `nbstripout` to handle Jupyter?

0

Support worktree commands from a bare repository

Max FERGER 3 years ago 0

When using worktrees, I like to have my main clone reside in a bare repository.

Like that, it stands out from the worktrees.

However, the Worktree submenu entries are disabled when looking at a bare repo in SmartGit 21.1.2 :-(

0
Declined

Re-add the "current line" DIFF pane at the bottom of the Changes pane

Justin W 3 years ago updated by Iulian Onofrei 1 year ago 3

Previous versions of SmartGit showed a small pane at the bottom of the Changes pane which showed the DIFF of the current/selected line. After upgrading to the new version (which supports Unified and Side-by-side DIFF), that "current line diff" pane is gone, and I cannot find any options/settings to re-enable it. Please add it back. It is a VERY useful feature, especially when the main Changes pane is in side-by-side mode (since you simultaneously get the best of both modes).

0
Completed

"Search for Repositories" usability issues

Matt 3 years ago updated 3 years ago 3

"Search for Repositories" usability issues

I want to bring all the repos on a given drive into the Repositories list, grouped by parent folder, using the "Search for Repositories" function. This is proving to be very difficult.


Here are the issues I have found:

  • The list of repos in the "Search for Repositories" dialog is initially pre-populated with some, but not all, repos on the filesystem. It is unknown which paths have been searched to produce this initial list. There is no way to clear these initial results.
  • Choosing a search location and performing a search leaves this initial set of repos polluting the search results. The found repos are mixed in with the initial selection, which is unhelpful and confusing.
  • The search results cannot be sorted.
  • There is no way to specify which group - if any - the selections will be added to. In fact, it seems completely arbitrary where the added repos will end up. I found that even though I might create a new group and select it before running the search, sometimes the repos will be added to a different group, or no group at all. If they end up in the wrong group, the result is a complete mess, and we may as well delete everything and try to start again.

Here are some ideas that might improve the experience:

  • Clear the list of found repos when a manual search is performed, so that the results only include the requested search results.
  • Either do not pre-populate the list of found repos, or indicate which paths have been searched to produce it.
  • Provide a way to specify which group the repos will be added to. This could be achieved by providing the option to choose a target location at the end of the Search for repositories dialog.
    • This could also be achieved if a "Find and add repositories" context command were provided on the Repositories list, i.e. when right-clicking on an existing group, or right-clicking on no item.
  • Allow the list of found repos to be sorted by path and/or selection status.


0

Ability to set default JQL query in .gitbugtraq

jflag 3 years ago 0

When selecting a JIRA issue (on commit) SmartGit uses a default JQLquery to find available issues in JIRA.

It would be nice if the default query could be set/overridden in the .gitbugtraq file, this would make it easier for developers coming onto a project who might otherwise have to tweak the JQL in order to get appropriate issues.

Perhaps this already is available? However I couldn't find any documentation on optional .gitbugtraq parameters.