Repo sync

content/apps/creating-github-apps/writing-code-for-a-github-app/index.md

@@ -19,6 +19,5 @@ children:
   - /building-a-login-with-github-button-with-a-github-app
   - /building-a-cli-with-a-github-app
   - /setting-up-your-development-environment-to-create-a-github-app
-  - /creating-ci-tests-with-the-checks-api
+  - /building-ci-checks-with-a-github-app
 ---
-

content/rest/checks/index.md

@@ -17,6 +17,6 @@ children:
 autogenerated: rest
 ---
 
-You can create apps that perform continuous integration, code linting, or code scanning services and provide detailed feedback on commits. For more information, see "[AUTOTITLE](/rest/guides/using-the-rest-api-to-interact-with-checks)" and "[AUTOTITLE](/apps/creating-github-apps/writing-code-for-a-github-app/creating-ci-tests-with-the-checks-api)."
+You can create apps that perform continuous integration, code linting, or code scanning services and provide detailed feedback on commits. For more information, see "[AUTOTITLE](/rest/guides/using-the-rest-api-to-interact-with-checks)" and "[AUTOTITLE](/apps/creating-github-apps/writing-code-for-a-github-app/building-ci-checks-with-a-github-app)."
 
 <!-- Content after this section is automatically generated -->

content/rest/guides/using-the-rest-api-to-interact-with-checks.md

@@ -19,6 +19,8 @@ Rather than binary pass/fail build statuses, {% data variables.product.prodname_
 
 For an example of how to use the REST API with a {% data variables.product.prodname_github_app %}, see "[AUTOTITLE](/apps/creating-github-apps/guides/creating-ci-tests-with-the-checks-api)."
 
+You can use statuses with [protected branches](/rest/repos#branches) to prevent people from merging pull requests prematurely. For more information, see "[AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches#require-status-checks-before-merging)."
+
 ## About check suites
 
 When someone pushes code to a repository, GitHub creates a check suite for the last commit. A check suite is a collection of the [check runs](/rest/checks#check-runs) created by a single GitHub App for a specific commit. Check suites summarize the status and conclusion of the check runs that a suite includes.

data/reusables/apps/accept_new_permissions_steps.md

@@ -1,2 +1,2 @@
 1. Click **Save changes** at the bottom of the page.
-1. If you've installed the app on your account, check your email and follow the link to accept the new permissions. Any time you change your app's permissions or webhooks, users who have installed the app (including yourself) will need to accept the new permissions before the changes take effect. You can also accept the new permissions by navigating to your [installations page](https://github.com/settings/installations) and clicking on "Configure" next to your app. You'll see a banner at the top of the page letting you know that the app is requesting different permissions. Click "Details" and click "Accept new permissions."
+1. If you've installed the app on your account, check your email and follow the link to accept the new permissions. Any time you change your app's permissions or webhooks, users who have installed the app (including yourself) will need to accept the new permissions before the changes take effect. You can also accept the new permissions by navigating to your [installations page](https://github.com/settings/installations). You'll see a link under the app name, letting you know that the app is requesting different permissions. Click "Review request", and then click "Accept new permissions."