Will look into that. Thanks!

Yes I can see how that might be the case.

I have seen this happen with many people new to Git--during my time getting my EE degree, and now, working as a test engineer.

So in my mind, it seems like a common enough pitfall for beginners that a decent number of people might appreciate this feature.

Particularly those who only code on occasion, but are not really employed as programmers, as is fairly common in integration/system testing for embedded systems and PLC hardware.

I do not have a great feel for SmartGit's customer base.

At my job site, SmartGit seems to be used more as a way to keep things simple and minimize the need to learn the inner workings of Git on teams that are primarily composed of engineers and technicians.

Perhaps it is instead mainly targeting power users who are looking to save time versus trying to manage large projects through the CLI.

Whatever the case, I appreciate your consideration and taking the time to give me your honest feedback.

It seems as though I will need to do some more investigation about why this has been such a common issue on our team; then brainstorm about possible changes to our workflow or other strategies to help mitigate the problem.

Hello Marc and Thomas,

I do not know if you get some type of notification for replies on older topics.
So this might going out into the ether, but do either of you have any feedback for me on the likelihood of my request being implemented?

I see that it has been several months since any suggestions were accepted and implemented.

So I am left wondering if there is interest in my idea, but it is just waiting for an appropriate point in the development schedule to be incorporated, or if my request never had any hope of being accepted.

I would appreciate any feedback you could provide.

And thank you either way.