[Bug?] [Feature Request] Support for Triggering Azure Pipelines in Merge Queue #145538
Replies: 3 comments
-
💬 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 ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
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. ⭐ |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Bug
Body
Currently, our enterprise project relies on Azure Pipelines to run PR checks. To enhance main branch protection, we want to leverage the merge queue functionality. However, the pipelines are not triggered when a PR enters the merge queue, despite both PR triggers and CI triggers being enabled for the pipelines.
This creates a gap in validation, as queued PRs are not rechecked before merging. We would like GitHub to collaborate in enabling support for triggering Azure Pipelines when using the merge queue, ensuring robust branch protection and seamless CI/CD workflows.
Beta Was this translation helpful? Give feedback.
All reactions