From 449a9242ac0bde44d72715a5f55d80669ffc550f Mon Sep 17 00:00:00 2001 From: Laura Coursen Date: Mon, 7 Nov 2022 13:05:44 -0600 Subject: [PATCH] Add :nail_care: --- .../troubleshooting-required-status-checks.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md b/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md index 801c50bfa2..5a6d3d43e3 100644 --- a/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md +++ b/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md @@ -112,7 +112,7 @@ Now the checks will always pass whenever someone sends a pull request that doesn {% endnote %} {% ifversion fpt or ghes > 3.3 or ghae > 3.3 or ghec %} -## Required status checks from unknown sources +## Required status checks from unexpected sources It's also possible for a protected branch to require a status check from a specific {% data variables.product.prodname_github_app %}. If you see a message similar to the following, then you should verify that the check listed in the merge box was set by the expected app.