On Sun, 17 Apr 2016 08:04:37 -0700 (PDT) Lars Persson <larsp77...@gmail.com> wrote:
> One purpose of git is that if I make a change and the program doesn't > work, you would like to go back to the version that worked. > > What is the recommended/best way to do this if you have gitHub? > > Would it be to simply choose the working version on gitHub? > > Or maybe do a checkout <commit-id>? > > I am really new at this. Please read a book on Git first. Your question is very basic, and this most probably demonstrates lack of understanding of basic concepts behing a version control system. But concepts cannot be effectively created in your mind by following a simple Q&A session -- you have to actually read and understand some background material on the topic. So I highly recommend to read at least a single book on Git. And before embarking on a book, you could read [1]. ...and while we're at it, I, for one, think that the most crucial properly of version controlling systems is not the ability to "go back in time" in case of an error found but actually finding when an offending change was made, and what was the rationale for it. So don't underestimate the necessity to make small atomic commits and writing good explanatory commit messages. The Git project itself is an exemplary example of how to do both -- check its history out. 1. http://tom.preston-werner.com/2009/05/19/the-git-parable.html -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
