3 ms·
The github GUI for Mac/Windows solves this problem completely, by hiding the vast majority of git's power-user features. (No stage, no no tracking branches, no
by dfabulich 14y ago
The github GUI for Mac/Windows solves this problem completely, by hiding the vast majority of git's power-user features. (No stage, no no tracking branches, no manual rebasing.)
- stickfigure 14y agoOh, how I wish this were so! Even with fairly boring usage, the Github GUI periodically wedges my repository into a state which requires CLI interaction (and a trip to stackoverflow). It's even worse for newbies - I get desperate pleas for help from clients all the time. I have come to the conclusion that there is no way around teaching the command line first, then giving them the Github client after they achieve competence.
- dfabulich 14y agoCan you repro that?
- stickfigure 14y agoCan I repro giving the Github client to newbies and getting desperate pleas for help soon afterwards? Yes, it's consistent :-) No, I have not tried to reproduce the incidents which screwed up my repository. After a few harrowing experiences I pretty much gave up using the Github for Mac client for anything except basic commits. And even that screws up - I frequently have to commit files twice; it's like the client only stages some of the files, even though they're all checked. If my commits are large I usually go to the command line to avoid the double commit msgs. I'm about to give up entirely.
- sbierwagen 14y agoIt... really shouldn't be doing that. What is your precise workflow?
- jeremyjh 14y agoI don't think this is really for programmers though is it? I thought this was more about content/documentation developers.
- recursive 14y agoIt looks like it's for programmers to me.
- benatkin 14y agoI believe it's Tower that plays that role. I know a designer who uses it, who would be bewildered by the CLI git.