-
Notifications
You must be signed in to change notification settings - Fork 309
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GitHub Comments for Merge Queue #4663
Comments
hey @MaximilianoAdaro , thanks for bringing up the topic. I'll talk with the team internally and get back to you as soon as possible 😄 |
@MaximilianoAdaro to make sure we understand:
you'd like the results from Something like
|
That's right @juan-fernandez |
I understand. This would be a feature request. Let me get back to you once we have prioritized it.
If you "trick" the datadog library into thinking it runs in the source branch (the one about to be merged) instead of |
I was wondering if it's possible to send a |
that's not currently possible. The way we'll proceed here is by attempting to detect |
Hello @juan-fernandez! |
hey @MaximilianoAdaro, sorry, no updates yet |
Hi Team,
I'm currently using
dd-trace-js
in my GitHub Actions workflows and have successfully integrated Datadog GitHub comments for pull requests. However, I am facing challenges when trying to enable GitHub comments for the Merge Queue (MQ) level.The goal is to have Datadog post comments on GitHub pull requests that are part of the Merge Queue, similar to how it works for individual pull requests. This would greatly enhance our visibility and traceability during the merge process.
Could you please provide guidance or best practices on how to achieve this? Are there specific configurations or environment variables that need to be set to enable GitHub comments for the Merge Queue?
An example here, the branches starting with
gh-readonly-queue/master/...
are the one from the MQAny help or pointers would be greatly appreciated! cc @juan-fernandez
Thank you!
The text was updated successfully, but these errors were encountered: