Things I wish everyone knew about Git (Part I)
blog.plover.com
Things I wish everyone knew about Git (Part I)
1–10 of 200 posts
Re: Things I wish everyone knew about Git (Part I)
#2A great video tutorial on Version Control for Code Using Git: https://www.youtube.com/watch?v=mndB6zHmU3k
And Managing Code Projects with Git Branching: https://www.youtube.com/watch?v=tzJDZY1x31I
Re: Things I wish everyone knew about Git (Part I)
#3haha, i cant count the times i fucked up and i just copied my files out, rm -rf repo; git clone; copy in :)
Re: Things I wish everyone knew about Git (Part I)
#4I'm pleased the coming Part II purports to point to `reflog`. For a tool that _looks_ like it's fairly advanced, this is one of my favorites to show juniors, because it works so well as a "get me back to where I was" hack.
Re: Things I wish everyone knew about Git (Part I)
#5I wonder how many hours have been wasted on fixing mistakes made on git. Recently, I watch a friend spend two days try and figure out what the junior Devs have done with commits and branches
Re: Things I wish everyone knew about Git (Part I)
#6The definition of a branch here does not seem useful in any way.
Re: Things I wish everyone knew about Git (Part I)
#7Fwiw a branch isn't a named sequence of commits, it's just a label that points to a single commit. It's exactly the same as a tag except that git moves it when you make a new commit.
Mercurial calls these bookmarks which IMO is a much better name because it works exactly like real bookmarks (in books, not browsers). A git branch feels a little bit like a branch of a tree because each commit points to their parent. Therefore, you don't need to track the entire sequence of commits in the branch but just the commit at the tip. I think if they'd had named only this concept better, Git would've been way easier to grok.
I wouldn't usually nitpick like this but given that the entire point of this article is it matters to get the basic concepts right, I figured the author might want to get this basic concept right.
Re: Things I wish everyone knew about Git (Part I)
#8Can’t wait for part 2, way to be a tease, author!
Re: Things I wish everyone knew about Git (Part I)
#9Fwiw a branch isn't a named sequence of commits, it's just a label that points to a single commit. It's exactly the same as a tag except that git moves it when you make a new commit. Mercurial calls these bookmarks which IMO is a much better name because it works exactly like real bookmarks (in books, not browsers). A git branch feels a little bit like a branch of a tree because each commit points to their parent. Th…
> each commit points to their parent
Potentially more than one.
Re: Things I wish everyone knew about Git (Part I)
#10Fwiw a branch isn't a named sequence of commits, it's just a label that points to a single commit. It's exactly the same as a tag except that git moves it when you make a new commit. Mercurial calls these bookmarks which IMO is a much better name because it works exactly like real bookmarks (in books, not browsers). A git branch feels a little bit like a branch of a tree because each commit points to their parent. Th…
> each commit points to their parent Potentially more than one.
just to spell it out fully for dear reader: that's how merge commits work.