You're reading from Accelerate DevOps with GitHub Enhance software delivery performance with GitHub Issues, Projects, Actions, and Advanced Security

Product type Paperback

Published in Sep 2022

Publisher Packt

ISBN-13 9781801813358

Length 540 pages

Edition 1st Edition

Tools

GitHub

Concepts

DevOps

Author (1):

Michael Kaufmann

View More author details

Table of Contents (31) Chapters

Preface

1. Part 1: Lean Management and Collaboration

2. Chapter 1: Metrics That Matter FREE CHAPTER

3. Chapter 2: Plan, Track, and Visualize Your Work

4. Chapter 3: Teamwork and Collaborative Development

5. Chapter 4: Asynchronous Work: Collaborate from Anywhere

6. Chapter 5: The Influence of Open and Inner Source on Software Delivery Performance

7. Part 2: Engineering DevOps Practices

8. Chapter 6: Automation with GitHub Actions

9. Chapter 7: Running Your Workflows

10. Chapter 8: Managing Dependencies Using GitHub Packages

11. Chapter 9: Deploying to Any Platform

12. Chapter 10: Feature Flags and the Feature Lifecycle

13. Chapter 11: Trunk-Based Development

14. Part 3: Release with Confidence

15. Chapter 12: Shift Left Testing for Increased Quality

16. Chapter 13: Shift-Left Security and DevSecOps

17. Chapter 14: Securing Your Code

18. Chapter 15: Securing Your Deployments

19. Part 4: Software Architecture

20. Chapter 16: Loosely Coupled Architecture and Microservices

21. Chapter 17: Empower Your Teams

22. Part 5: Lean Product Management

23. Chapter 18: Lean Product Development and Lean Startup

24. Chapter 19: Experimentation and A|B Testing

25. Part 6: GitHub for your Enterprise

26. Chapter 20: GitHub – The Home for All Developers

27. Chapter 21: Migrating to GitHub

28. Chapter 22: Organizing Your Teams

29. Chapter 23: Transform Your Enterprise

30. Other Books You May Enjoy

Chapter 11: Trunk-Based Development

One of the capabilities that are highly correlated with accelerated engineering velocity is trunk-based development (also known as TBD). High-performing teams have fewer than three active branches at any time, and their branches have a short lifetime (less than a day) before being merged into the main branch (Forsgren N., Humble, J., and Kim, G. 2018, page 98). Unfortunately, TBD is not a git workflow but rather a branching model of choice that has been in use since the 80s. It is not well defined and leaves a lot of room for interpretation, especially when it comes to using it with GitHub. Also, I personally find that only moving to a trunk-based workflow does not increase the performance too much. Only large teams with a highly complex workflow that are already stuck in merge hell really have this high impact. For most teams, it is more a combination of different capabilities such as feature flags and continuous integration/continuous deployment...