fix: allow absolute paths to Dangerfile

[buffcode]

Problem

We are using Danger within a Docker-container in our CI pipeline. As most of our pipelines use a central Danger configuration as well as standardized CI pipelines, Danger is not required to be setup in every single repository, but fully baked into our container.

The Dangerfile is placed alongside the required dependencies in a different path (/app) than the actual project (/workdir).

When running DangerJS with --dangerfile /app/dangerfile.mjs the path is joined with path.cwd(), resulting in an invalid path like /workdir/app/dangerfile.mjs.

Solution

Switching to path.resolve instead of path.join resolves (pun intended) this, without impacting other use cases.

[orta]

Cool, this makes sense to me