A way for dangerfile to detect whether is running on CI

[stellarhoof]

We've got rules that make sense to only run when on CI. Currently there's no way of detecting this without duplicating the logic danger already uses to detect if it's running in CI.

When I say CI I mean real CI, not the fake one. Perhaps this information could be exposed under danger.utils ?

[orta]

Yeah, that makes sense danger.utils.info.isCI maybe? Then we can add something like isGitHub, or isLocal later on

[stellarhoof]

I'd say danger.utils.info.ci.*, so we've got a nice namespace there. What does the "You Can Do This" tag mean? That is easy to contribute on this issue?

[orta]

I'm cool with that - it means someone doesn't have to feel blocked on implementing because we agree on the general idea 👍

[milesj]

https://www.npmjs.com/package/env-ci ?

[orta]

Yep good point, you're welcome to use that in your Dangerfiles - I'd rather not have a new dependency in Danger unless it provides something really new and useu