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!
Log: ability to search inside files of the selected commit (grep)
Sometimes I'd like to search the (all, not just the modified ones) files of the commit currently selected in the Log window. This may be useful if a method does not existing any more but you know a state where it existed.
Bitbucket(Server): enable "Create pull request" for from the main window.
When I select a branch in the Branches tab, Review > Create Pull Request is still grayed out. But it's available in the same menu in the log window. Please enable "Create pull request" for Bitbucket server from the main window.
I can do everything needed to create and prepare the feature branch for the pull request in the main window, but then for the last step as a feature developer I need to open a different window, look for my feature branch again, and finally open the pull request. This is a disruption
in the workflow.
(Reviewing the pull request (fetch, look at commits, comment, approve ;-), merge) is another workflow, usually by a different person - it's okay that this happens in the log window, as we
need the log for that.)
Output view: use fixed width font in
It's easier to read console responses in a fixed width font.
Also, some remotes respond with ascii art that looks terrible in variable width fonts. OK this isn't a major issue, but still...
Log and journal: Branch color determined by recognized pattern/keyword in the branch name
recognized keywords/pattern in the branch name.
Ex:
- 'Develop' and 'Master' will have their color set to the color configured
for the 'Develop' and 'Master' keyword respectively;
- Feature branches would have their color set based on the color configured
for the 'Feature/' pattern;
- Other branch <-> pattern could be configured to fill the user needs;
- Closed/deleted branches would revert back to gray.
Spell-checker: optionally prevent commit with typos
It would be great if SmartGit could be configured so it doesn’t allow to commit until I fix all of the spelling problems in the commit message.
This way, if I have a typo, it will make sure I noticed it. This, of course, should be optional.
Rebase: support autostashing working tree changes
Rebase ("Rebase HEAD to", "Rebase Interactive From") fails because of not stashed changes. It would be great to autostash/unstash files as for Pull-rebase feature.
Push: add --no-verify checkbox so we can skip githooks
Right now you can only skip verify with commits, add this feature to push as well
Allow submodule to be added in new sub-directory
Currently the submodule configuration disallows adding a submodule in a non-existent directory. If I want to add a new submodule in externals/foo_project, for example, it doesn't let me do that in one step.
File log and repo log should be represented as separated commands in the UI
I often find confusing to open repo log when I have a file selected. I end up opening file log, then I realize this, close it, unselect the file and reopen the log.
I think that two separate buttons would be good. The file one should be grayed out when no file is selected.
show BOM state in Changes window
How about to show the state and change of BOM(byteorder mark) in the Changes window.
It is tedious work to check whether the byte order mark is in the desired state.
Customer support service by UserEcho
