When multiple commits are pushed together, the workflow runs on second last commit causing build to stuck with "Expected — Waiting for status to be reported"

[jzmalik123]

Select Topic Area

Bug

Body

Issue Summary: When multiple commits are pushed in quick succession, the workflow sometimes runs on the second-to-last commit rather than the latest one. As a result, the build status remains in a "Expected — Waiting for status to be reported" state for the most recent commit, causing the build to become stalled and unresponsive.

Steps to Reproduce:

Push a series of commits to a branch in quick succession.
Observe that the GitHub Actions workflow sometimes initiates on a previous commit rather than the latest one.
Notice that the build status on the latest commit remains as "Expected — Waiting for status to be reported" indefinitely.
Expected Behavior: The GitHub Actions workflow should trigger on the latest commit of a push, ensuring that the build status reflects the current state of the branch and allows for seamless merging and deployment processes.

Observed Behavior: The workflow frequently picks up the second-to-last commit, leading to a "stuck" status on the latest commit. This delays the build process and requires manual intervention to re-run the workflow, causing workflow inefficiencies and potential deployment delays.

Impact:

Development velocity is hindered as engineers must manually re-run workflows for correct build status.
Stuck workflows can delay deployment processes, impacting feature releases and bug fixes.
Potential misalignment in code review and CI/CD processes as outdated builds may not accurately represent the latest code changes.

Additional Information: This issue seems more likely to occur when there are multiple rapid commits, which may point to a race condition in how workflows are triggered on new pushes. We would appreciate any guidance or recommendations on configuration adjustments or other workarounds to ensure that workflows consistently trigger on the latest commit.
After the cancellation of the workflow on the latest commit, following error shows on the latest commit annotation:

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