Github Stacks [Merge as Stack] Webhooks

[ghthor]

🏷️ Discussion Type

Product Feedback

Body

When merging multiple PRs in a stack together (using merge as stack) there is only one webhook emitted for the push event to the trunk branch.

This breaks CI assumptions that any commit pushed to the trunk branch would emit a push event, enabling a CI system to get triggered for each commit to the trunk.

Merge As Stack breaks this assumption as now multiple PRs are being merged and only emitting a single webhook after being merged.

In my particular use case, I manage a monorepo that performs change impulse calculations per commit to trunk (to isolate the CI workload to the minimal set caused by the commit contents). With GH stacks pushing multiple PR's into trunk and only emitting a single webhook, my CI impulse calculations are now broken as they only get a single push event webhook triggered by the top of stack (top of merge PR).

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