You are signed in. Close

You are signed out. Close

Thank you. Your subscription has started. Close

Thank you. You will get an email when a new comic comes out. Close

We could not confirm your payment. If you paid, use the link "Sign in" at the bottom of the page. Close

Something went wrong on our side. Please try again in a moment. Close

Previous episode Pipeline stages: why a CI pipeline runs the fastest checks first

How CI/CD works: why releasing code every day is safer than once a month

Pull requests and branch protection: how a team keeps main green

On many software teams, nobody can push straight into the main branch. Every change waits at a locked door. What that door is, and what has to happen before it opens.

  1. 1 This time, you do not merge into main yourself. You push your short branch to the shared repository and open a pull request: a request to merge it into main, where the team can see your change.youbooking-screenpushsharedrepositoryPull request:merge booking-screeninto main?

    This time, you do not merge into main yourself. You push your short branch to the shared repository and open a pull request: a request to merge it into main, where the team can see your change.

  2. 2 A pull request alone stops nothing. Anyone could still press merge while the checks are running, or push straight to main.Pull requestchecksrunningMergeRono

    A pull request alone stops nothing. Anyone could still press merge while the checks are running, or push straight to main.

The rest of this episode is for subscribers

Subscribe to read every premium episode. You can cancel when you want.

Paid yearly: $99 instead of $119.88

Next episode Build artifacts: why you build an app once and ship that same copy

Share this comic

More comics