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

Accelerating with MyFlow

As you can see, git workflows are just a collection of solutions for different use cases. The main difference is in whether they are trunk-based or not and if they are explicit about some things or not. As I find all workflows lacking something, I created my own workflow: MyFlow.

MyFlow is a lightweight, trunk-based workflow based on PRs. MyFlow is not a new invention! Many teams already work this way. It is a very natural way to branch and merge if you focus on collaboration with PRs. I just gave it a name, and I can see people picking it up easily.

The main branch

Since MyFlow is trunk-based, there is only one main branch called main, and it should always be in a clean state. The main branch should always build, and it should be possible to release it to production at any time. That's why you should protect main with a branch protection rule. A good branch protection rule would include at least the following criteria: