danger / danger/danger

Attempt to update the commit status for GitLab builds

Open
#509 0 comments 2 reactions 1 assignee Claimed by @JuanitoFatas View on GitHub
Enhancement GitLab You Can Do This
Dominant language
Ruby
Stars
5.7k
Forks
488
PR merge metrics
No merged PRs in 30d

Description

When GitLab is used to as the backing scm provider try to call the [API](http://docs.gitlab.com/ce/api/commits.html#commit-status) to update the status of the commit. Handle 403/404 failures gracefully and continue running even if the call fails. This will allow users who are in a position to run danger with developer permissions to do so and gracefully degrade for users that run danger with guest or reporter permissions.

cc @orta

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.