6 ms·
Actually, source control GUIs are excellent for less-technical team members. I've had great results using TortoiseSVN or the GitHub client with multiple distrib
by pygorex 14y ago
Actually, source control GUIs are excellent for less-technical team members. I've had great results using TortoiseSVN or the GitHub client with multiple distributed teams.
It's great to be able to tell a new team member: "Press this button to get everyone else's updates." "Press this button to push your updates to the server/current branch." Later, depending on their role and level of skill, we can cover branching, merging, tagging and other move advanced features.
- rogerbinns 14y agoMy experience has been that developers using a gui make better commits. It is far easier to see what the changes are, see unintended code changes, make a more useful message and only pick a relevant subset of changed hunks. The command line only folks tend to do 'git commit -a' or equivalent and have messy noisy commits. Yes a highly skilled developer at the top of their game, paying attention to every detail and pumped full of caffeine is far less likely to do that, but they are rare.