Live data from Hacker News

Githug - an interactive way to learn how to use git

github.com

11–20 of 32 posts

Re: Githug - an interactive way to learn how to use git

#11
post #9

I can't quite get past level 4: "Set up your git name and email, this is important so that your commits can be identified" I had already set these up in my global config, but I ran the following commands anyway: git config user.name "My Name"; git config user.email "my_name@myemail.com" Looking at the code, it seems that the program is supposed to ask me for my name and email, but it never did.

Me as well. It's never been edited other than the commit so it's not like there was an update. I am on a mac if that matters.

edit: what you can do is edit the .profile.yml file and change :level to clone and under the completed levels area you can add - config to bypass it.

edit2: it looks like it does not work well on the mac as any level that asks a question is not doing so.

Re: Githug - an interactive way to learn how to use git

#12
post #9

I can't quite get past level 4: "Set up your git name and email, this is important so that your commits can be identified" I had already set these up in my global config, but I ran the following commands anyway: git config user.name "My Name"; git config user.email "my_name@myemail.com" Looking at the code, it seems that the program is supposed to ask me for my name and email, but it never did.

Tried playing around and got stuck at the same level. The hint in this case is not very useful unfortunately: "These settings are config settings. You should run `git help config` if you are stuck"

Re: Githug - an interactive way to learn how to use git

#13
You got me...I got sucked into playing this tonight :) Very clever, you were able to get me to poke around with things I hadn't tried yet. Thanks for providing the reset option, I made a mistake at level 12 and it really came in handy. I'm now at level 20 and it looks like I'm supposed to add a level to the game ;)

Re: Githug - an interactive way to learn how to use git

#14
post #9

I can't quite get past level 4: "Set up your git name and email, this is important so that your commits can be identified" I had already set these up in my global config, but I ran the following commands anyway: git config user.name "My Name"; git config user.email "my_name@myemail.com" Looking at the code, it seems that the program is supposed to ask me for my name and email, but it never did.

I have the same error on mac as well. I don't see anything wrong with the code for interact, it's just a print and gets.

Re: Githug - an interactive way to learn how to use git

#17
post #5
post #4

I like that people are learning Git, but why are there so many tutorials for it? The Git commands that are most useful 95% of the time just didn't seem that hard to learn, IMO. It's not worth wasting memory for the other 5% of the time because I'll probably need to check the man pages anyway.

I haven't had a chance to checkout Githug yet, but for me, as a former SVN user, the switch to Git was daunting. I can't really explain why, but wrapping my head around DVCS took an embarassingly long time. For those that I point to Git now, especially those that are semi-technical, it's really useful to also point them to a nice intro. As with all new things, lowering any barrier to entry is usually a good thing.

> I can't really explain why, but wrapping my head around DVCS took an embarassingly long time.

Git's UI being complete shit probably helped there.

Re: Githug - an interactive way to learn how to use git

#18
post #5

Earlier quoted context omitted.

I haven't had a chance to checkout Githug yet, but for me, as a former SVN user, the switch to Git was daunting. I can't really explain why, but wrapping my head around DVCS took an embarassingly long time. For those that I point to Git now, especially those that are semi-technical, it's really useful to also point them to a nice intro. As with all new things, lowering any barrier to entry is usually a good thing.

> I can't really explain why, but wrapping my head around DVCS took an embarassingly long time. Git's UI being complete shit probably helped there.

For Mac, I've found this version of GitX to be really good:

http://gitx.laullon.com/

Re: Githug - an interactive way to learn how to use git

#19
post #5
post #4

I like that people are learning Git, but why are there so many tutorials for it? The Git commands that are most useful 95% of the time just didn't seem that hard to learn, IMO. It's not worth wasting memory for the other 5% of the time because I'll probably need to check the man pages anyway.

I haven't had a chance to checkout Githug yet, but for me, as a former SVN user, the switch to Git was daunting. I can't really explain why, but wrapping my head around DVCS took an embarassingly long time. For those that I point to Git now, especially those that are semi-technical, it's really useful to also point them to a nice intro. As with all new things, lowering any barrier to entry is usually a good thing.

In my case this was because Git has a model of version control that is nowhere as straightforward as SVNs and several hundred command line options without any good indication of what to do when.

We also had a lot of problems with what I think of as "Linux Arrogance" - the person who took the lead on rolling out git refused to even try to help anyone not using git in a bash shell, which is an issue when all the devs are .net developers with no cygwin experience.

Once you can figure out the commands you need to use git is very nice, but it's a nightmare to start and requires a big mental step backwards to teach someone with no exposure to it.

Re: Githug - an interactive way to learn how to use git

#20
This is topical for me right now, and apologies in advance that I'm going to link back again to my blog at the end of this comment...

I've been thinking recently about how important it is to dominate your tools. Use git regularly? Then learn the shit out of it. Learn how it works in side and out.

Over the last few days I've been committing the entirety of http://book.git-scm.com/ to memory, and many little inefficiencies I never knew were there are now gone.

Committing stuff like this to memory is easy and fun: http://www.writemoretests.com/2012/02/how-to-remember-everyt...

Post reply on HN