-
-
Notifications
You must be signed in to change notification settings - Fork 363
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
If DangerID is defined, use it as the context for platform status #840
Conversation
|
||
let name = "Danger" | ||
if (process.env["PERIL_INTEGRATION_ID"]) { | ||
name = "Peril" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to support this use case in Peril? I'm not familiar enough with it to know if it's possible to run multiple instances.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nope, or at least whatever we need to do it'd be a bit of work on Perils side 👍
@orta Can you take a look at the test failure here? It looks like it might not be related to my changes, but if it is let me know |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, cool, looks like the CI issue was just temporary 👍
|
||
let name = "Danger" | ||
if (process.env["PERIL_INTEGRATION_ID"]) { | ||
name = "Peril" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nope, or at least whatever we need to do it'd be a bit of work on Perils side 👍
Awesome, thanks @orta! Any estimate of when this will be published? It'll help us plan whether to go forward with a workaround or wait 😄 |
Oh, nevermind, Peril answered me, haha 👍 |
Resolves #839.
Currently, if you run two separate danger builds with their own IDs, they will post two separate comments. However, the status is not tied to the ID, so if one danger build fails and the second one passes, your PR will incorrectly be marked as passing.
This change uses the ID as the
context
/name
for the status, which will allow each build to show up as an independent status, making it possible to have multiple Danger runs on one PR. (We use this to run our build and test in parallel in the CI and report issues from each of them.)