Intermittently refs/pull/*/merge are not created (race condition)

[mnaoumov]

Select Topic Area

Bug

Body

There is a project obsidian-releases where certain actions are executed when PR is created.

Most of the times it works correctly but sometimes, it fails See job run

/usr/bin/git -c protocol.version=2 fetch --no-tags --prune --no-recurse-submodules --depth=1 origin +refs/pull/4692/merge:refs/remotes/pull/4692/merge
  Error: fatal: couldn't find remote ref refs/pull/4692/merge

It looks like the action was executed before the actual ref was created.

It seems to be a race condition.

Reproduction Steps

As it seems to be a race condition issue, there is no way to provide steps to reproduce for sure.

1. Create PR in https://github.com/obsidianmd/obsidian-releases/
2. See if job run failed. If no, go to Step 1

---

P.S. I am not a maintainer of the above mentioned repo

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

[mnaoumov]

Also sometimes it works if you close and reopen the PR, but it doesn't work all the time.
Rebasing the PR seems to work all the time.