Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

The Ship Show: Branching, Merging, and Octopi (Oh My!)

DZone's Guide to

The Ship Show: Branching, Merging, and Octopi (Oh My!)

· DevOps Zone ·
Free Resource

Can you release faster without sacrificing quality? See how with our free ebook Strategies for a Successful Test Automation Project and a free trial of Ranorex Studio today!

With the explosion in popularity and usage of Git and its distributed version control brethren, developers finally have cheap, easy, local branching. But branching is pointless without merging, and many organizations are finding that Git's free-for-all merge process can leave your organization with (mostly by being totally silent on the subject) code that is error-prone and doesn’t scale, and may even destroy content! As you search for the perfect branching model, questions like “should we use fast-forward merges or merge commits?”, “when do we rebase (if ever)?” and “what repository structure should we use?” are bound to crop up, along with “can’t we just use Git flow?” Join the panel as they grab a razor and a yak and talk:

Branching, Merging, and Octopi (Oh My!)

Join J. Paul Reed, aka @SoberBuildEng, Youssuf El-Kalay, aka @buildscientist, EJ Ciramella, aka @eciramella, Sascha Bates, aka @sascha_d, and Seth Thomas, aka @cheeseplus plus the last couple of weeks in News & Views and a Tool Tip!

Download Episode 27, or any of our previous shows!

Show Links/Notes

Tool Tip

Paul reviews Storm, a tool to “manage your SSH like a boss!”

Join Us!

What branching and merging models do you like? Which ones do you despise?

Or do you just hope you don’t have to worry about any of it?

Join the discussion!


Get your test automation project off to the right start. Download your free test planning template and a 30-day no-obligation trial of Ranorex Studio today!

Topics:

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}