June 2023
Intermediate to advanced
48 pages
1h 4m
English
Content preview from What Is Trunk-Based Development?
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.
Chapter 5. But What About...
As mentioned in Chapter 1, full CTBD can be controversial. There are many questions and objections, so in this section I’m addressing the ones I hear most often.
How Can I Get My Code Reviewed Without Branches and Pull Requests?
Some people use branches to hold new code until their peers can review it and then merge the code back into the main branch. They often ask, “If you’re not using branches, how do you hold code back for review?”
The two main benefits of code reviews are that they allow teams to review code changes to verify quality and they give developers an opportunity to see one another’s code.
And then there are pull requests. In case the concept is unfamiliar, pull requests (PRs) are a feature of the Git version-control system that allows developers to alert one another when particular branches are ready for review. Many teams use PRs to implement and formalize their code reviews, with rules that no one can merge code into the main branch without first going through a PR. And when teams are distributed, particularly across multiple time zones, PRs are a convenient way to facilitate asynchronous code review.
But treat code reviews, and in particular PRs, with caution. They can introduce significant problems related to speed, quality, and trust—as discussed in the following sections.
Code Reviews Delay Integration
You could say that the need for code review is an argument in favor of branches, but I would rather turn this on its head and ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access
More than 5,000 organizations count on O’Reilly
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.Julian F.
I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.Addison B.
I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.Amir M.
I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.