A successful Git branching model » nvie.com. Published: January 05, 2010 In this post I present the development model that I’ve introduced for all of my projects (both at work and private) about a year ago, and which has turned out to be very successful.
I’ve been meaning to write about it for a while now, but I’ve never really found the time to do so thoroughly, until now. Git Cheatsheet. Stash workspace index local repository upstream repository.
Git 102 - Adventurous. Secure source code hosting and collaborative development - GitHub. Help.GitHub - Welcome. Learn git one commit at a time. My Git Workflow. Lately I’ve been acting as the unofficial Git consultant for Skribit, usually in response to @Stammy saying something on Twitter along the lines of “Hey, git just did something totally nonintuitive and now I can’t figure out what to do next.”
I’ve been using Git long enough to know the answer, usually, or at least to be able to figure it out, plus I still remember how people used to SVN think, which helps. I think I’ve mentioned before how much I love Git. I’ve been a version control geek for a really long time: I remember getting way too excited about a feature that was like ‘git cherry-pick’ in some proprietary VCS we evaluated in 2000 or 2001. I still say that Darcs is the one I wish we had settled on, but I’ve grown to love Git over the past year or so, especially with GitHub making some of the rough spots so much easier. Moving a git repository subdirectory to its own repository at Mike Chambers. I use Git and GitHub to manage all of my personal code projects.
This will make it easier to track issues, as well as give me the option of open sourcing it and allow others to create and submit forks. <! Gitorious. Git-cheat-sheet-large.png (3300×2550) Git. Git Quick Reference. Git Community Book. Table of Contents.