Check suite events from GitHub Actions appearing in my personal GitHub App

[zakisk]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Github Apps

Body

Summary

My personal GitHub App, jerel-app, receives the expected check_run and check_suite webhook events for checks it manages. However, it also receives events for checks managed by the GitHub Actions app.

For example, I received a check_run event with:

• action: created
• check_run.status: completed
• check_run.conclusion: skipped
• check_run.app.slug: github-actions
• check_run.check_suite.app.slug: github-actions

The check is associated with a GitHub Actions workflow run, but the webhook delivery was sent to jerel-app.

Question

Is it expected for a GitHub App subscribed to check_run and/or check_suite events to receive events created by other apps, such as GitHub Actions?

If so, is filtering by check_run.app.id / check_suite.app.id the intended way to process only checks owned by my app?

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[abozaralizadeh]

Yes, this is expected, and filtering on the app id is the way to do it.

check_run and check_suite webhooks go to every GitHub App installed on the repo that has the "Checks" permission, not only to the app that owns the check. Only two action types are limited to the owning app:

• check_run.rerequested: "Only the GitHub App that someone requests to re-run the check will receive the rerequested payload."
• check_run.requested_action: sent to the app whose button the user clicked.

created and completed have no such limit, so you also get them for checks made by the GitHub Actions app (like your skipped one). See the check_run and check_suite events. The checks guide also says GitHub "sends the check_suite event (with requested action) to all GitHub Apps that have the checks:write permission".

You also can't turn the subscription off if your app has write access to Checks: such apps "are automatically subscribed to this webhook event".

So drop anything that isn't yours early in the handler. Use the numeric App ID rather than the slug:

const MY_APP_ID = Number(process.env.APP_ID);

if (name === "check_run" && payload.check_run.app.id !== MY_APP_ID) return;
if (name === "check_suite" && payload.check_suite.app.id !== MY_APP_ID) return;

Does that match what you see after adding the filter?

[RudraBhungaliya]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Github Apps

Body

Summary

My personal GitHub App, jerel-app, receives the expected check_run and check_suite webhook events for checks it manages. However, it also receives events for checks managed by the GitHub Actions app.

For example, I received a check_run event with:

• action: created
• check_run.status: completed
• check_run.conclusion: skipped
• check_run.app.slug: github-actions
• check_run.check_suite.app.slug: github-actions

The check is associated with a GitHub Actions workflow run, but the webhook delivery was sent to jerel-app.

Question

Is it expected for a GitHub App subscribed to check_run and/or check_suite events to receive events created by other apps, such as GitHub Actions?

If so, is filtering by check_run.app.id / check_suite.app.id the intended way to process only checks owned by my app?

Here is a direct answer tailored for that GitHub Discussion:

Yes, this is the intended and expected behavior on GitHub.

When a GitHub App is granted the Checks permission and subscribes to check_run and/or check_suite webhook events, GitHub delivers webhooks for all check runs created in repositories where your app is installed—regardless of which app created them (including GitHub Actions, third-party CI apps, or other custom integrations).

1. Why does this happen?
   GitHub delivers repository-level check events to all installed integrations with the appropriate permissions so that custom apps can monitor overall workflow statuses, trigger secondary pipelines, or build aggregated reporting dashboards across all checks running on a repository.

2. Is filtering by app.id / app.slug the intended approach?
   Yes, absolutely. Filtering incoming webhook payloads by check_run.app.id (or check_suite.app.id) against your own app’s ID is the standard best practice recommended by GitHub for processing only self-owned checks.

Here is an example snippet for handling incoming webhooks:

JavaScript
app.webhooks.on('check_run', async ({ payload }) => {
// Ignore checks created by other apps (e.g., github-actions)
if (payload.check_run.app.id !== MY_APP_ID) {
return;
}

// Handle your app's check runs here
});
If this helps answer your question, please mark it as the accepted answer!

[RudraBhungaliya]

Here is a direct answer tailored for that GitHub Discussion:

Yes, this is the intended and expected behavior on GitHub.

When a GitHub App is granted the Checks permission and subscribes to check_run and/or check_suite webhook events, GitHub delivers webhooks for all check runs created in repositories where your app is installed—regardless of which app created them (including GitHub Actions, third-party CI apps, or other custom integrations).

1. Why does this happen?
   GitHub delivers repository-level check events to all installed integrations with the appropriate permissions so that custom apps can monitor overall workflow statuses, trigger secondary pipelines, or build aggregated reporting dashboards across all checks running on a repository.

2. Is filtering by app.id / app.slug the intended approach?
   Yes, absolutely. Filtering incoming webhook payloads by check_run.app.id (or check_suite.app.id) against your own app’s ID is the standard best practice recommended by GitHub for processing only self-owned checks.

Here is an example snippet for handling incoming webhooks:

JavaScript
app.webhooks.on('check_run', async ({ payload }) => {
// Ignore checks created by other apps (e.g., github-actions)
if (payload.check_run.app.id !== MY_APP_ID) {
return;
}

// Handle your app's check runs here
});
If this helps answer your question, please mark it as the accepted answer!