When multiple workflows are triggered via workflow_dispatch on the same commit SHA, the GitHub UI merges the checks and annotations from all runs, instead of displaying them separately per workflow run.

[Pruthvijp051]

Why are you starting this discussion?

Bug

What GitHub Actions topic or product is this about?

Workflow Configuration

Discussion Details

Summary

When multiple workflows are triggered via workflow_dispatch on the same commit SHA, the GitHub UI merges the checks and annotations from all runs, instead of displaying them separately per workflow run.

Steps to Reproduce

1. Create two workflow files: .github/workflows/a.yml and .github/workflows/b.yml
2. Both use workflow_dispatch as a trigger.
3. Trigger both manually for the same commit SHA (can vary input parameters).
4. Observe the Checks and Annotations tab in the Pull Request or Commit view.

Actual Behavior

• Checks and annotations from both workflows are merged together.
• It is unclear which workflow produced which check/annotation.

Expected Behavior

• Each workflow run, even if triggered on the same commit SHA, should have its own set of checks and annotations, visible separately in the UI.

Environment

• GitHub Actions
• Runner type: [Hosted/Private]
• Workflow files: [attach examples]

Additional Context

• Related issue #1461

[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. ⭐

[kumvprat]

Any updates on this ?

[INikolOFF]

When you trigger multiple workflows on the same commit SHA using workflow_dispatch, GitHub’s UI combines the checks and annotations from all workflow runs under the same commit. This means you don’t see each workflow run separately in the commit’s checks view; instead, the results are merged together, which can make it harder to distinguish which workflow produced which annotations or failures.

Currently, there’s no way to force GitHub to display them separately for the same commit SHA; each workflow run is tied to the commit, and the UI aggregates their status and annotations. A common workaround is to trigger workflows on different refs or tags if you need separate, distinct check displays.