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.
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.
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.
Git's UI being complete shit probably helped there.
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..
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.
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.
Update This is fixed in 0.1.4
Anyway, level 18 is incorrect. the CHUNK does indeed start on line 23, but the line changed is the line 26
If you are unsure, you can type `githug hint` to get a hint.
The solution for the first level is `git init`
I hope this helps you on your way.
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.
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?
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...