Short description of the talk
Branches create distance between developers. This distance is about the integration of code from multiple components in massive, long-lived pull requests that are often just turns to be a headache for all team members.
In the trunk-based development model, all developers work on a single branch with open access to it. Often it’s simply the main branch. They commit code to it and run it. It’s super simple. And a lot of fun.
In this talk we will review pros and cons of using trunk-based development model vs Git Flow, and decide which one is better fit Ruby specific projects.
Short description of the talk Branches create distance between developers. This distance is about the integration of code from multiple components in massive, long-lived pull requests that are often just turns to be a headache for all team members.
In the trunk-based development model, all developers work on a single branch with open access to it. Often it’s simply the main branch. They commit code to it and run it. It’s super simple. And a lot of fun.
In this talk we will review pros and cons of using trunk-based development model vs Git Flow, and decide which one is better fit Ruby specific projects.
Level
Contact information
Possible days for the talk