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 we (Syntevo) and other users will understand what you want. A plain request "SmartGit should look cool" is too vague because we don't know what we should change, and hence will not be approved by us.
Thank you for your help!
A pimped changes fiew would be nice, so I don't need to start it via beyond compare to see the facts. Most importent is the reducing to changes (diff view in bc - whith adjustable pre and post code parts) and to hide changed comments / whitespaces (triv. button in bc - with selectable: whitespace/ comments / case changes,....)
Sometimes I use the index editor to do partial commits as follow:
- Open the index editor
- Do a partial stage
- Commit 1
- Do another partial stage
- Commit 2
- Do another partial stage
- Commit 3
The point is that after the first commit, the index editor still shows the modifications that went in the first commit, while I would like the option to refresh the status of the index editor in order to only show the modifications between the working tree and the HEAD (now at commit1).
If one has to do 10 commits in this way, leaving also the committed changes (as it is now) makes the workflow quite confusing. The only solution, for now, is to close and reopen the index editor after each commit in order to achieve the result desired.
TL;DR: Add a button to refresh index editor after commit as it happens if one closes and reopens the index editor after commit.
I've submitted this via email to the developer but I think it is worth putting it here as well.
When working on a new feature or fix my expected work flow is to pull the base branch (master, develop, etc.) then create a new feature or hotfix branch, make the changes and commit them to the new branch. Then a peer review or pull request is made for other developers to review the changes before they get merged back into the base branch. However sometimes when working on some new code I forget to create the new branch. When I finish the change and commit it, it gets committed back to the base branch directly. This is bad since is skips the peer review step.
It would be very nice if I could configure SmartGit to warn me if I am attempting to commit a change to a base branch (in my case that would be the master or develop branches). That warning would remind me that I forgot to create a new branch before doing the commit, and would help be to avoid occasionally forgetting to create the new branch, and mistakenly committing changes directly to the base branch.
- I would like to review only 11 files (a set).
- When I select them and click to compare, it opens a new window for every file.
- It also ask me "do you really want to open >10 windows?".
- Please allow me to use the size of my monitor (full-screen mode would be nice as well) and to compare many files in the same time (each file is in a new tab?).
- Please also display the repository name.
- Please allow me to see the relative to the root path, instead of filename.ext. (a new settings option?)
I have copied my files from windows to ubuntu and all the files which are already committed & pushed into the repo showing modified.
Customer support service by UserEcho