Book Image

Accelerate DevOps with GitHub

By : Michael Kaufmann
Book Image

Accelerate DevOps with GitHub

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)
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

Role-based access

At the repository level, you can grant role-based access to teams or individual people. You can use one of the following default roles:

  • Read: Read and clone repositories. Open and comment on issues and pull requests.
  • Triage: Read permissions, plus manage issues and pull requests.
  • Write: Triage permissions, plus read, clone, and push to repositories.
  • Maintain: Write permissions, plus manage issues, pull requests, and configure some repository settings.
  • Admin: Full access to repositories, including sensitive and destructive actions.

Note that the read role can do more than just read! It can open and comment on issues and pull requests. Triage and maintain are typical roles in open source projects. They are not so commonly used in enterprise scenarios.

You can set a base permission for an organization to read, write, or admin. This will grant all members the corresponding permission to all repositories. Outside collaborators do not inherit...