This post originated from an RSS feed registered with Java Buzz
by Mathias Bogaert.
Original Post: Git: The “T” is for “team!”
Feed Title: Scuttlebutt
Feed URL: http://feeds.feedburner.com/AtlassianDeveloperBlog
Feed Description: tech gossip by mathias
You’ve probably heard about the awesome workflow capabilities that Git can offer you. But you may be asking yourself, “How can a version control system that just stores my code history really be that helpful?” The answer is all in the workflows. For many teams, some of the most pressing development questions can be addressed with a proper workflow: Are all the features completed for the next release? Are we missing any commits? Has everybody reviewed the new code? Does every team member know where to check in the code for a hotfix of the current version? Will the build run successfully when merging the changes into master? For teams that tend to answer “no” to some (or all) of these, Git workflows might be the answer. After all, who doesn’t want to work more efficiently together as a team? See the presentation Earlier this year we gave a presentation at JavaZone in Oslo explaining how teams at Atlassian have built successful workflows with Git. Different products and teams need different workflows; in the talk we discuss how at Atlassian, the Bitbucket team’s Git workflow is completely different than the Stash team’s. The talk also covers how you can successfully use forks to protect your codebase, what Gitflow is all about, and how adding continuous integration to the mix makes your feature, release, and develop branches much more stable. The video The slides But wait, there’s more! If you want to know more about the individual workflows presented in this talk, check out our tutorials. You can also subscribe to our monthly Git newsletter and get the newest and hottest information on distributed version control. Learn more
Previous Topic
