Update troubleshooting-rules.md (#53916)

Co-authored-by: Copilot <[email protected]>
Co-authored-by: Sophie <[email protected]>

Author: 3 people

content/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/available-rules-for-rulesets.md

@@ -147,6 +147,8 @@ After enabling required status checks, all required status checks must pass befo
 
 Any person or integration with write permissions to a repository can set the state of any status check in the repository, but in some cases you may only want to accept a status check from a specific {% data variables.product.prodname_github_app %}. When you add a required status check rule, you can select an app as the expected source of status updates. The app must be installed in the repository with the `statuses:write` permission, must have recently submitted a check run, and must be associated with a pre-existing required status check in the ruleset. If the status is set by any other person or integration, merging won't be allowed. If you select "any source", you can still manually verify the author of each status, listed in the merge box.
 
+To troubleshoot issues with configuring status checks in rulesets, see [AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/troubleshooting-rules#troubleshooting-required-status-checks).
+
 {% ifversion repo-rules-enterprise %}
 
 > [!NOTE] For organization-level status checks, the app must be installed with the `statuses:write` permission. Only apps with this permission are displayed when configuring rulesets at the organization-level.
@@ -161,7 +163,7 @@ You can think of required status checks as being either "loose" or "strict." The
 | **Loose** | The **Require branches to be up to date before merging** checkbox is **not** checked. | The branch **does not** have to be up to date with the base branch before merging. | You'll have fewer required builds, as you won't need to bring the head branch up to date after other collaborators merge pull requests. Status checks may fail after you merge your branch if there are incompatible changes with the base branch. |
 | **Disabled** | The **Require status checks to pass before merging** checkbox is **not** checked. | The branch has no merge restrictions. | If required status checks aren't enabled, collaborators can merge the branch at any time, regardless of whether it is up to date with the base branch. This increases the possibility of incompatible changes.
 
-For troubleshooting information, see [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/troubleshooting-required-status-checks).
+For status check troubleshooting information, see [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/troubleshooting-required-status-checks).
 
 {% ifversion code-scanning-merge-protection-rulesets %}
 

content/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/troubleshooting-rules.md

@@ -19,6 +19,23 @@ If a branch or tag is targeted by rules restricting the metadata of commits, you
 
 When utilizing push rulesets, a maximum of 1000 reference updates are allowed per push. If your push exceeds this limit, it will be rejected. For more information see [AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/creating-rulesets-for-a-repository#creating-a-push-ruleset).
 
+## Troubleshooting required status checks
+
+When defining status checks, the name format depends on the type of check:
+
+* **Workflow**: The name format is `<job name>`.  
+* **Reusable workflow**: The name format is `<job name> / <reusable job name>`.  
+* **Other checks**: The name format is `<check name>`.
+
+Required status checks do not take workflow, matrix, or event trigger types into account.
+
+{% ifversion repo-rules-enterprise %}
+
+Status checks are not indexed for rulesets defined above the repository level. You must manually enter the exact check name expected.
+
+For rulesets in evaluate mode, a status check will run on the targeted branch but will not be required to pass.
+{% endif %}
+
 {% ifversion repo-rules-required-workflows %}
 
 ## Troubleshooting ruleset workflows