Skip to content

Commit 2663219

Browse files
authored
Merge pull request #237 from justwriteclick/ag-fixes
Update to label file examples
2 parents 3ab8f66 + f1e5836 commit 2663219

File tree

2 files changed

+3
-1
lines changed

2 files changed

+3
-1
lines changed

_learn/12-ssg-performance.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: "Static Site Generator performance considerations"
33
layout: learn
44
image:
55
path: /images/learn/ssg-performance.png
6-
thumbnail: /images/learn/ssg-performance-400×225.png
6+
thumbnail: /images/learn/ssg-performance-400x225.png
77
---
88

99
When you start building large documentation sites, or gluing together multiple documentation sets, you might look for performance gains in the build time. Having smaller doc sites helps with this, so that you can build with your static site generator systems in parallel, but also look for incremental builds or ways to measure build times to look for areas where the build is slowed down and then find a root cause for the slower performance.

_posts/articles/2023-10-01-protecting-codeowners-file.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -21,6 +21,7 @@ A `CODEOWNERS` file can be stored in a directory, or in the `.github` folder, wh
2121

2222
A straightforward example involves protecting the `docs` folder in the `main` branch, where the `main` branch is the branch used to publish the documentation. In this example, the org name is `justwriteclick` and the username is `annegentle`. You would name the file `CODEOWNERS` and store it in a `docs` directory.
2323

24+
Example `CODEOWNERS` file:
2425
```
2526
@justwriteclick/annegentle
2627
```
@@ -33,6 +34,7 @@ Then, make sure that the branch is protected using the repository's **Setting**
3334

3435
To see an example of this setup, look at the Microsoft 365 community documentation repository at https://github.com/MicrosoftDocs/microsoft-365-community/. The `CODEOWNERS` file contains a team name, `@microsoftdocs/officedocs-admin`, and those team members can review and merge the list of documents in the `CODEOWNERS` file. The documents contain configuration information as well as the `CODEOWNERS` file itself.
3536

37+
Example `CODEOWNERS` file from MicrosoftDocs:
3638
```
3739
docfx.json @microsoftdocs/officedocs-admin
3840
.openpublishing.build.ps1 @microsoftdocs/officedocs-admin

0 commit comments

Comments
 (0)