Skip to content

Write an excerpt for the protected branch writeup #235

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
annegentle merged 3 commits into from
Oct 2, 2023
Merged

Write an excerpt for the protected branch writeup #235

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
41ec3a4
Write an excerpt for the protected branch writeup
annegentle Oct 2, 2023
3d46dc9
Fix image file from png to jpg
annegentle Oct 2, 2023
5f7fcf9
Fix relative image reference
annegentle Oct 2, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions _posts/articles/2023-10-01-protecting-codeowners-file.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,13 +1,13 @@
---
layout: post
title: "Protecting a Branch so Only the Docs Team Merges and Publishes"
excerpt: .
excerpt: When you want to allow the docs team members to maintain docs within a code repo, while giving the docs team autonomy over their own reviews and merges, you can use a protected branch and a CODEOWNERS file.
last_modified_at: Sun Oct 1 11:05:31 CDT 2023
categories: articles
author: annegentle
tags: [cicd, reviews, docs, settings, GitHub]
image:
path: /images/guarded-lightbulb-rob-sinclair.png
path: images/guarded-lightbulb-rob-sinclair.jpg
caption: "[Lightbulb in a protective cage, Attribution: Rob Sinclair.)"
comments: false
share: true
Expand Down