On Sat, Aug 11, 2012 at 10:33 PM, Alex Harui <aha...@adobe.com> wrote:
> > > > On 8/11/12 2:45 AM, "Carlos Rovira" <carlos.rov...@codeoscopic.com> wrote: > > > Hi Alex, > > > > great to see you on Git now! :) > > > > > > When you want to plan a feature make a local branch to make your > > development, better than start to make it directly on the initial branch. > Why is using a local branch important? > > > When you finish, merge with final. You can as well publish your feature > > branch in remote to let others see it and help with your feature. > > > > You must take into account that commits should be atomic in order to be > > > > Another great thing of Git is that when a released is planned the rest of > > the time can continue working and commiting work without the need to > > "freeze" commits due to the distributed nature of the system :) > Is this because of a branching strategy or is there something about Git > that > makes this easier? > > > Because in Git, you "commit" locally. Only when you do a "push", the remote repo is updated. Here is a nice article explaining the concepts [1] [1] http://gitready.com/beginner/2009/01/21/pushing-and-pulling.html
