Skip to content

Commit 05a5506

Browse files
committed
Move note before ruleset settigns screenshot for improved visibility
1 parent a850ec0 commit 05a5506

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/wiki-guide/When-to-think-about-branch-protections.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -50,9 +50,9 @@ As with branch protections, it is also possible to set the rules for branches ma
5050
You can also edit branch rulesets from this page.
5151
The example below shows the addition of a branch ruleset that requires a pull request and that it be approved prior to merging. It also will remove approval if other changes are added that require approval. This is equivalent to the branch protection example given above.
5252

53+
!!! note "Note"
54+
If your site is generated from `main`, you should create a separate ruleset for `gh-pages` that protects against deletions and force pushes (but does not require PRs). This is relevant when generating a site with tools like MkDocs.
55+
5356
![Rules checklist](images/GH-branch-protections/382113942-39fd79d4-ff95-404b-86c4-8ab875cc9a4b.png){ loading=lazy }
5457
/// caption
5558
///
56-
57-
!!! note "Note"
58-
If your site is generated from `main`, you should create a separate ruleset for `gh-pages` that protects against deletions and force pushes (but does not require PRs). This is relevant when generating a site with tools like MkDocs.

0 commit comments

Comments
 (0)