developers work locally and push branches to the central repo.a workflow that defines a strict branching model designed around the project release.We’ll also take a look at how I use SourceTree and Visual Studio together. So long story there…to put in in very short terms one of the best things with git is the branching model and speaking about branching, Git Flow is a very popular such a “branching workflow model” that we’ll be taking a look at now and how to use the built-in support that SourceTree offers for it. Still in beta it still does an excellent job at most cases (and it’s free just like git). The tooling is still pretty basic but I think for most cases it does do a good job.Ĭoming from TFS-land however, I still missed the Source Control Explorer so I was very pleased to learn about SourceTree from Atlassian which is a GIT UI for Windows. However I do encourage people coming into git from TFS to learn the command-line first before using a UI.Īgain, being a Microsoft guy, I do like my UIs so I was very pleased when Microsoft finally revealed that they where now supporting git in Visual Studio 2012. Switching to git really forced me to get to learn the git command-line (yeah, git relies heavily on the command-line). My favourite way of describing the difference between the TFS and Git branching models is as follows, in TFS – branching is essentially like the TV Show Fringe in that you have to deal with parallel worlds crossing between those world is a difficult process with severe health risks to the person “crossing over”, whereas with Git is more like Doctor Who: branching is essentially dealing with time streams where you can easily go forwards, backwards and even sideways. Coming from a Microsoft environment with first Source Safe and later on TFS (or TFVC really) it was a bit of a leap to take from Centralized Version Control to Distributed Version Control since that is really the biggest leap to take (I think).Įndjin has very good way of describing the difference as: However, a couple of months ago I started using git (or github if I should be completely honest…but that’s based on git) for version control. I like their products, development tools, the whole lineup really. You can change this in Preferences now to other defaults (e.g. Added support for default push options other than ‘matching branches’.In addition to bug fixes, we’ve added a couple more of the features you’ve asked for. Take complete control over your code - the way it should be. Highlight the changes you want to undo and click reverse. Whether you want to reverse a change made in a line, a chunk of code, or an entire file, SourceTree 1.5 now gives you that power. Sometimes, you need to revert a change that you made, but undoing an entire commit can be painful. Reverse Granular Changes from Previous Commits Easily collaborate on code using SourceTree and Bitbucket. SourceTree now gives you options to configure Teams settings when you create a hosted repository. SourceTree 1.5 now lets you adopt this model, so you can unclutter your repository and develop stress-free.īitbucket Teams let you create a shared account in Bitbucket to consolidate your team-owned repositories and organize your group’s work. He’s taken your feedback and pushed out some of the features you’ve asked for in the latest release – SourceTree 1.5!Ī development model first published by nvie, Git-flow (and its Mercurial equivalent – Hg-flow) organizes your repositories by formalizing the use of feature branches, releases, and hot-fixes. In the last couple months, he’s even traveled to San Francisco from his hometown in the UK, hosting a drinkup to meet SourceTree customers face to face. Steve Streeting has made it his mission to reach out to SourceTree users and listen to what they have to say.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |