Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Similar to the support of Jenkins commit hash. Fixes the same problem as fixed in 73d1439: > Danger doesn't currently have a way to understand on which commit is > running. To get the current commit it asks to the platform the list of > commits on the PR and assumes that is running on the last one. This > creates few problems when you push a new commit before Danger runs on > the CI for the previous commit, because it will assume is running on > the last one, but that is actually not true, and that means that both > the status update and the commit hash in the Danger comment signature > will be wrong.
- Loading branch information