Actions bug fixes for the week of Feb 5, 2024 (#49136)

Author: jc-clark

content/actions/using-workflows/events-that-trigger-workflows.md

@@ -387,7 +387,10 @@ on:
 
 {% note %}
 
-**Note**: {% data reusables.developer-site.multiple_activity_types %} Although only the `checks_requested` activity type is supported, specifying the activity type will keep your workflow specific if more activity types are added in the future. For information about each activity type, see "[AUTOTITLE](/webhooks-and-events/webhooks/webhook-events-and-payloads#merge_group)." {% data reusables.developer-site.limit_workflow_to_activity_types %}
+**Notes**:
+
+- {% data reusables.developer-site.multiple_activity_types %} Although only the `checks_requested` activity type is supported, specifying the activity type will keep your workflow specific if more activity types are added in the future. For information about each activity type, see "[AUTOTITLE](/webhooks-and-events/webhooks/webhook-events-and-payloads#merge_group)." {% data reusables.developer-site.limit_workflow_to_activity_types %}
+- {% data reusables.actions.merge-group-event-with-required-checks %}
 
 {% endnote %}
 
@@ -397,6 +400,8 @@ For example, you can run a workflow when the `checks_requested` activity has occ
 
 ```yaml
 on:
+  pull_request:
+    branches: [ "main" ]
   merge_group:
     types: [checks_requested]
 ```

content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue.md

@@ -37,7 +37,7 @@ You **must** use the `merge_group` event to trigger your {% data variables.produ
 
 {% note %}
 
-**Note:** If your repository uses {% data variables.product.prodname_actions %} to perform required checks on pull requests in your repository, you need to update the workflows to include the `merge_group` event as an additional trigger. Otherwise, status checks will not be triggered when you add a pull request to a merge queue. The merge will fail as the required status check will not be reported. The `merge_group` event is separate from the `pull_request` and `push` events.
+**Note:** {% data reusables.actions.merge-group-event-with-required-checks %}
 
 {% endnote %}
 

data/reusables/actions/merge-group-event-with-required-checks.md

@@ -0,0 +1 @@
+If your repository uses {% data variables.product.prodname_actions %} to perform required checks {% ifversion repo-rules-required-workflows %}or if you require workflows via organization rulesets {% endif %}on pull requests in your repository, you need to update the workflows to include the `merge_group` event as an additional trigger. Otherwise, status checks will not be triggered when you add a pull request to a merge queue. The merge will fail as the required status check will not be reported. The `merge_group` event is separate from the `pull_request` and `push` events.