Pull Request Merge Events No Longer Generated in Events API

[uhourri]

Select Topic Area

Product Feedback

Body

Following the October 2025 Events API changes, my tool ghmap, which maps low-level events to contributor activities, has encountered a critical regression.

Previously, a PullRequestEvent with action: closed and payload.pull_request.merged: true allowed us to detect the "MergePullRequest" activity. Now, no event is generated when a pull request is merged. We can detect when a PR is closed, but the pivotal action of merging has become invisible in the event stream.

This is not a payload reduction; it is the removal of a key activity signal. It breaks any analysis that tracks completed work, distinguishes between closure and acceptance, or measures contributor impact through merges. For ghmap, an entire high-level activity category is now missing.

Request: Please restore the generation of an event signal when a pull request is merged. If the full PullRequestEvent payload is costly, a minimal event with just the id, number, and merged: true flag would restore functionality for all downstream analysis and automation tools.

(Link to related discussions: #177111, #177735, #178788)

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

[AlexandreDecan]

This is also impacting valuable data sources for researchers, such as https://www.gharchive.org. Only pull requests being closed (without a merge) are still visible, while pull requests being merged aren't at all. At least a PullRequestEvent with action=closed should be generated for those pull requests (or even better, with action=merged).

[maniac103]

There now is a PullRequestEvent with action being merged, but

• the existence of that action is not documented
• the actor field for those events is set to the PR owner, while it (at least IMHO) should be set to the user who merged the PR (after all it's them who acted in that moment)