You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just updated to the latest danger (0.13.0) and looks like something isn't quite right.
I'm not sure exactly when this call was made, but I am using Codeship. This may have something to do with API changes that the codeship provider relied on.
yarn danger v0.21.3
$ danger
Error: TypeError: prs.find is not a function
at Object.<anonymous> (<project>/node_modules/danger/distribution/ci_source/ci_source_helpers.js:90:39)
at step (<project>/node_modules/danger/distribution/ci_source/ci_source_helpers.js:32:23)
at Object.next (<project>/node_modules/danger/distribution/ci_source/ci_source_helpers.js:13:53)
at fulfilled (<project>/node_modules/danger/distribution/ci_source/ci_source_helpers.js:4:58)
at process._tickCallback (internal/process/next_tick.js:109:7)
error Command failed with exit code 1.
The text was updated successfully, but these errors were encountered:
Intertesting, could getPullRequests ever return a non-array type? In any case, lodash.find is in danger dep tree, replacing it with that would be a trivial fix
Just updated to the latest danger (
0.13.0
) and looks like something isn't quite right.I'm not sure exactly when this call was made, but I am using Codeship. This may have something to do with API changes that the codeship provider relied on.
The text was updated successfully, but these errors were encountered: