Re: [Discuss] Teaching Git with Github Desktop

2016-09-06 Thread Matthew Gidden
Hi everyone, Thank you all for the great discussion. I played with the other GUIs mentioned in the thread and very much like gitkracken (puns aside). It seems to have a nice balance between an intuitive interface, a reasonably close representation of the CLI, and an agnostic backend. To provide

Re: [Discuss] Moving thread to Github Issue: " Teaching Git with Github Desktop"

2016-09-06 Thread Cameron Macdonell
Hi everyone, Thank you for the lively discussion. I've created a github issue https://github.com/swcarpentry/git-novice/issues/340 for further discussion Please continue the discussion there. Please focus on ways that one can use GUI tools and recommendations (such as

Re: [Discuss] Teaching Git with Github Desktop

2016-09-06 Thread Schneider, Juliane
Oscar never had to use Git! Juliane. Sent from Mail for Windows 10 From: P Lijnzaad Sent: Tuesday, September 6, 2016 8:35 AM To: Bennet Fauber Cc: Software Carpentry

Re: [Discuss] Teaching Git with Github Desktop

2016-09-06 Thread Thomas Ballinger
Re: this additional complexity Rochelle points out is introduced by git GUIs, the sixth git command I generally teach (after git init, add, commit, status, and log) is `gitk --all`. This is a git gui that typically comes with git installations, and critically is essentially a *read-only* GUI.

Re: [Discuss] Teaching Git with Github Desktop

2016-09-06 Thread Juan Nunez-Iglesias
Hi all, Sorry, in all honesty I didn't mean to start a flame war; I just thought as instructors we would agree on this point. =) Three points about *why* I think it's broken: 1) the entertaining and informative Git Koans: http://stevelosh.com/blog/2013/04/git-koans/ 2) a couple of additional

Re: [Discuss] Teaching Git with Github Desktop

2016-09-06 Thread Ivan Gonzalez
I think there are a few good points in this thread that justify why we teach the Git on the command line: 1. Different GUIs offer different experiences and would be hard to agree on one. 2. Git CLI is used to reinforce what's learned during the Unix shell lesson. 3. The very important use case of

Re: [Discuss] Teaching Git with Github Desktop

2016-09-06 Thread P Lijnzaad
I concur with Juan Nunez-Iglesias, the git command line interface is horrendously complicated (or should I say inconsistent *), even for experienced programmers. This is of course partly due to the git data model, which is also very complicated (with >= 5 places to mentally keep track of things:

Re: [Discuss] Teaching Git with Github Desktop

2016-09-06 Thread Bennet Fauber
> Git command line interface isn't friendly to new users This is different from 'broken'. Broken implies that it does not do what it claims it will. > because "git checkout" do too much for the same command > depending of what arguments the user pass. > Why do we can't have "git undo" that ony

Re: [Discuss] Teaching Git with Github Desktop

2016-09-06 Thread David Martin (Staff)
> Git command line interface isn't friendly to new users because "git checkout" > do too much for the same command depending of what arguments the user pass. > Why do we can't have "git undo" that ony works with the working copy? alias 'git undo' 'git checkout ...' > Why do we can't have

Re: [Discuss] Teaching Git with Github Desktop

2016-09-06 Thread Raniere Silva
Hi Steven, >> My two cents: the git command line interface is practically broken. I think >> there's consensus on this, especially on this list. As such, I'm strongly in >> favour of teaching git by GUI, because by and large GUIs have done a good job >> of simplifying the process of interacting

Re: [Discuss] Teaching Git with Github Desktop

2016-09-06 Thread Steven Koenig
On 09/06/2016 01:45 PM, Juan Nunez-Iglesias wrote: > Hi all, > > My two cents: the git command line interface is practically broken. I think > there's consensus on this, especially on this list. As such, I'm strongly in > favour of teaching git by GUI, because by and large GUIs have done a good

Re: [Discuss] Teaching Git with Github Desktop

2016-09-06 Thread Lukas Weber
I tried SourceTree on Mac but stopped using it due to the extremely small display font, which cannot be changed. I sent them some feedback (there are some long comment threads about exactly this issue) but I don't think it has been resolved so far. I also used GitKraken on Mac for a while. It was

Re: [Discuss] Teaching Git with Github Desktop

2016-09-06 Thread mail
Hi all, > This is, however, a recent policy of mine, so I've only tested it once, but > it was highly successful. I noticed a *huge* difference in how quickly > people caught on. Most people in the class were using Sourcetree, which is > available on both Windows and OS X, and I recommend it.

Re: [Discuss] Teaching Git with Github Desktop

2016-09-06 Thread Juan Nunez-Iglesias
Hi all, My two cents: the git command line interface is practically broken. I think there's consensus on this, especially on this list. As such, I'm strongly in favour of teaching git by GUI, because by and large GUIs have done a good job of simplifying the process of interacting with git. This

Re: [Discuss] Teaching Git with Github Desktop

2016-09-06 Thread E.W.
Hi Matt, Along the theme of item 2, Programming Historian already has a lesson on GitHub desktop, meant for being worked through alone. You may find some of their approaches of interest, particularly when code switching for a new population.

Re: [Discuss] Teaching Git with Github Desktop

2016-09-06 Thread Gerard Capes
(i.e., is it doing more harm by obfuscating the mechanics of the underlying tool)? This definitely can happen, especially when an IDE has a git plug-in (so not specifically talking about GitHub desktop). Clarity can be restored when using the command line to unpick the mess. There are sometimes

[Discuss] Teaching Git with Github Desktop

2016-09-06 Thread Matthew Gidden
Hi everyone, I searched the list history and didn't see a similar topic already posted, so apologies if this is a rehash of a previous conversation. I'm going to be teaching a version of the git novice lessons next week to an audience that does not feel comfortable on the command line. My goal