Copilot Code Review workflow causes check runs to be associated with the wrong workflow

[Makeshift]

Select Topic Area

Bug

Copilot Feature Area

Copilot in GitHub

Body

There is a very long standing feature request/bug which means that events resulting in multiple workflows being executed can cause check runs to be associated with the incorrect check suite.

Since Code Review now acts very similarly to a normal GitHub Actions Workflow execution, essential reports that we use as part of our rulesets as required checks are being associated with the Code Review workflow instead of the workflow that actually produced the checks.

This is now an issue in every repository in our org with Copilot Code Review enabled, so this has required either disabling Copilot Code Review or relying only on job success rather than check-runs in most repos.

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

[jackjamees6]

Thanks for breaking this down it’s a tricky issue with workflow associations. For anyone looking to take a break and unwind after debugging, 777sx game download play store latest version is a fun option that’s easy to get started with.