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.
Thanks for everyone who pointed this out. I'll check it out when I get my hands on a mac.
note Because solution is a Proc, you cannot prematurely return out of it and as a result, must put an implicit return on the last line of the solution block. Maybe not return , but you can `next`: `next true if repo.valid?` works fine within Procs.
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"
I guess the longer you've used a centralized approach, the more "intrenched" that way of thinking is, and the bigger the mental shift has to be.
Unlearning the old can be much harder than learning the new..
Funny how typing "githug" is a very mind twisting task. You end up with "github" even if you are thinking about the ending "g". Still a very clever name!
I have question on level 21, it said: Contribute to this repository by making a pull request on Github. The Hint: Forking the repository would be a good start! Could someone clarify a bit more?
The goal for the contribute level is for you to contribute something valuable to githug, such as a level or a bug fix.
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.
For me the lightbulb moment was seeing the data model explained (in "Git for computer scientists" for example). I'm not sure this can be conveyed in game form, and githug doesn't seem to go there. With close to a hundred commands that can be composed in various ways, teaching tasks isn't as worthwhile as teaching the principles.