Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Accelerate DevOps with GitHub
  • Toc
  • feedback
Accelerate DevOps with GitHub

Accelerate DevOps with GitHub

By : Michael Kaufmann
5 (11)
close
Accelerate DevOps with GitHub

Accelerate DevOps with GitHub

5 (11)
By: Michael Kaufmann

Overview of this book

This practical guide to DevOps uses GitHub as the DevOps platform and shows how you can leverage the power of GitHub for collaboration, lean management, and secure and fast software delivery. The chapters provide simple solutions to common problems, thereby helping teams that are already on their DevOps journey to further advance into DevOps and speed up their software delivery performance. From finding the right metrics to measure your success to learning from other teams’ success stories without merely copying what they’ve done, this book has it all in one place. As you advance, you’ll find out how you can leverage the power of GitHub to accelerate your value delivery – by making work visible with GitHub Projects, measuring the right metrics with GitHub Insights, using solid and proven engineering practices with GitHub Actions and Advanced Security, and moving to event-based and loosely coupled software architecture. By the end of this GitHub book, you'll have understood what factors influence software delivery performance and how you can measure your capabilities, thus realizing where you stand in your journey and how you can move forward.
Table of Contents (31 chapters)
close
1
Part 1: Lean Management and Collaboration
7
Part 2: Engineering DevOps Practices
14
Part 3: Release with Confidence
19
Part 4: Software Architecture
22
Part 5: Lean Product Management
25
Part 6: GitHub for your Enterprise

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:

  • Require a minimum...
bookmark search playlist download font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete