How do I make a single action, with multiple triggers, create only a single check?

[GabeMillikan]

Select Topic Area

Question

Body

I have created an action which processes a PR's labels and changed files to determine which and how many codeowner(s) need to review the PR. The details of how it works are not particularly important, but it needs to run on both pull_request and pull_request_review triggers since it depends on labels and reviews (respectively).

These triggers are currently causing two different checks to run, but I only need the latest check to pass. How can I combine both these checks into one, so that merging is allowed? (screenshot: first run fails, subsequent run succeeds under a different trigger)

Here's my .github/workflows/review-requirements.yml

name: Reviews
on: 
  pull_request:
    types: [labeled, unlabeled, opened, reopened, synchronize, review_requested, review_request_removed]
  pull_request_review:
    types: [submitted, edited, dismissed]


jobs:
  check_review_requirements:
    runs-on: ubuntu-latest
    name: Check Review Requirements
    steps:
      - name: Checkout Latest Code
        uses: actions/checkout@v4
      - name: Check Review Requirements
        uses: ./.github/actions/label-based-review-requirements
        with:
          token: ${{ secrets.GITHUB_TOKEN }}

and here's .github/actions/label-based-review-requirements/action.yml

name: 'Review Requirements'
description: 'Enforces review requirements based on the applied labels.'
inputs:
  token:
    description: GitHub Access Token. Will be used to fetch PR reviews.
    required: true
runs:
  using: 'node20'
  main: 'dist/index.js'

.github/actions/label-based-review-requirements/dist/index.js looks something kind of like this (actual logic removed)

if (!requiredReviewersApproved()) {
  core.setFailed("Need more appovals!");
}

The documentation doesn't say much about this.

[Hielamon]

I have the same confusion about this.

[Weinell]

What is the status on this? I face the same issue.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[mars]

I've tried using run-name, but that results in only the Actions tab name changing, not the checks in the PR.

[mattalbr]

Still facing this issue!

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[GabeMillikan]

This is obviously nonsense and AI generated.

[dpetzev]

It is actually mind-boggling how this is still an issue. Can't we have one event group like pull_request_events that includes both the pull_request_review and pull_request triggers

[anthony-hayes]

FYI I found a workaround for this: create a commit status from a workflow that runs on both pull_request_review and pull_request, and then do a status check in GitHub on the status name (the context value)
https://docs.github.com/en/rest/commits/statuses?apiVersion=2022-11-28#create-a-commit-status