16 ms·
To be fair, if you're going to lifehacker to help you set up github, you're probably not motivated enough to go tearing through github's faq. Quite frankly, you
by newishuser 14y ago
To be fair, if you're going to lifehacker to help you set up github, you're probably not motivated enough to go tearing through github's faq. Quite frankly, you're probably not motivated enough to finish the lengthy tutorial they posted.
- bradleyland 14y agoAgree completely. I'd extend that to say that if you're relying on Lifehacker to help you set up Git/Github, this statement is probably false: "Nevertheless, it's good to learn the old-fashioned way otherwise your options in the simplified software won't make sense." The Github app goes to great lengths to make the interaction with Github more intuitive than the CLI Git client. Yes, your options are more limited, but I work with several pseudo-technical users who use solely the Github app. You can switch branches, checkout, publish, delete, and merge through the Github app. The Github app even stashes automagically if you switch branches with uncommitted changes. The only area that gets sketchy are conflicts, but many of the people at whom this article is targeted will never encounter a conflict, because they're the sole developer. In any case, I can see absolutely no reason that a casual developer should move past the Github client to the Git CLI client if they have no specific need.
- dhruvmittal 14y agoI sort of regard lifehacker as a web site for teenagers and hobbyists nowadays, so I'm not particularly surprised at the quality and tone of their technical work.