November 2019
Intermediate to advanced
408 pages
9h 56m
English
While rollbacks are possible, as we've just seen, the general consensus should be that each new deployment moves forward. The code for a new release contains the code from the previous release, plus some small changes. Following the Git way of operating, we work on a single branch (the main branch) that gets pushed forward.
This means having to avoid several active long-lived branches. This model is called trunk-based development and it's the recommended way of working to aim for continuous integration. In a trunk-based development, feature branches are short-lived and are always merged with the main branch (or trunk), which is normally called the master in Git.
Read now
Unlock full access