http://nvie.com/posts/a-successful-git-branching-model/ 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. A successful Git branching model » nvie.com

A successful Git branching model » nvie.com

stash workspace index local repository upstream repository Git Cheatsheet

Git Cheatsheet

Git 102 - Adventurous
Secure source code hosting and collaborative development - GitHub Great collaboration starts with communication. Review changes, comment on lines of code, report issues, and plan the future of your project with discussion tools. Friction-less development across teams. Work with project collaborators or teams of people in organization accounts to communicate with ease.

Secure source code hosting and collaborative development - GitHub

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. My Git Workflow
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. I have one large repository called projects, which is then broken into sub directories based on the main technology used for each project (i.e. Flash, JavaScript, iphone, etc...). I am currently working on a Flash based iphone game code-named "pewpew", which is maintained within my projects repository. As I have begun to work on it more and more, I decided that I wanted to have pewpew in its own git repository. 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. <! Moving a git repository subdirectory to its own repository at Mike Chambers

Gitorious

Announcing Gitorious 3.0 Today we are proud and happy to announce the official release of Gitorious 3.0. This is a major upgrade which ships with a refreshed UI, a lot of improvements, and new features. It has been a huge effort by both the original Gitorious developers, who s... 18 Nov 19:16 Future of the “Inbox” feature The “Inbox” feature was added to Gitorious about 4 years ago and it was meant to give our users an easy way of communication. While we know it is a useful feature for many of you, we are also aware that it hasn’t gotten enough love recently. Gitorious
git-cheat-sheet-large.png (3300×2550)
git

Git Quick Reference