Associated Pull Requests to a commit returning an empty set

[arthurlm44]

Select Topic Area

Bug

Body

I've merged a GitHub PR in one of my private repos and it has merged successfully. In the web UI I can see the commit has three SHAs:

the SHA for the commit which is the head of master
two parent SHAs
The head of the new branch
The previous head of master
So far so good. The problem is when I query the data from the API one of the SHAs is missing.

the head.sha is correct
the base.sha is correct
the merge_commit_sha is null.
The API says the PR state is closed and merged is true.

What would cause the merge commit sha to be null? How can I help make sure it's set? My CI relies on having this data available.

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

[karl-cardenas-coding]

We are also seeing this with the the sorenlouv/backport-github-action tool, that is used for backports. It checks for a commit SHA and that's failing now due to this new behavior.

[ghthor]

We're also experiencing errors with a pull request that is still returning null as it's merge_commit_sha 2+ hours after it was merged into our main branch.

❯ gh api /repos/<obfuscated>/<obfuscated>/pulls/31177 | jq .merge_commit_sha
null

Thu Jan  2 17:20:36 2025 exit 0 🟢

[ghthor]

The next PR we merged has worked, but the one that was reporting null, is still reporting null

❯ gh api /repos/<obfuscated>/<obfuscated>/pulls/31180 | jq .merge_commit_sha
"<valid hash>"

Thu Jan  2 18:08:26 2025 exit 0 🟢

❯ gh api /repos/<obfuscated>/<obfuscated>/pulls/31177 | jq .merge_commit_sha
null

Thu Jan  2 18:08:35 2025 exit 0 🟢

[arthurlm44]

$ curl -L -H "Accept: application/vnd.github+json" -H "Authorization: Bearer $GITHUB_PAT" -H "X-GitHub-Api-Version: 2022-11-28" "https://api.github.com/repos/<obfuscated>/<obfuscated>/commits/d7e6f242c301268825749c57ec64aea7cc216b46/pulls"
[

]

[arthurlm44]

Looks like it's working on new PR's. Still getting an empty set on PR's created during the time window while this API endpoint was misbehaving.

[ghthor]

Yes, looks like we got an ack

https://github.com/orgs/community/discussions/148372#discussioncomment-11721313

[ghthor]

Updated response.

https://github.com/orgs/community/discussions/148372#discussioncomment-11721594