Is there any adequate reason for a manager to forbid the use of Git GUI Clients in a developer team.
I was talking to a friend about - let's call Foo Git GUI Client - all the features and how i was able to speed up some tasks and he said that any client is forbidden by the managers in his company.
Question is: Why?
A couple of reasons (on top of my mind):
- Security. A GUI Client can access private information in the company repository.
- Command knowledge. When the developer type the commands in Bash/CMD he exercises them.
- Blame the tool. A developer can put the blame on the tool about some error.
The trade-off here IMHO is control
You substitute commands in a Bash shell for a click in a GUI. You cannot be sure that the GUI is going to do exactly what you think it will do.
But even that, in a couple of tests it can be checked.