Skip to content

Clarify scopes required for DANGER_GITLAB_API_TOKEN

What does this MR do?

The Dangerbot documentation limitations - https://docs.gitlab.com/ee/development/dangerbot.html#limitations - say that you need to create a new API token but it doesn't mention what scopes are required by the token. This adds a single line explaining what scopes are required.

Screenshots (strongly suggested)

Does this MR meet the acceptance criteria?

Conformity

Availability and Testing

Security

Does this MR contain changes to processing or storing of credentials or tokens, authorization and authentication methods or other items described in the security review guidelines? If not, then delete this Security section.

  • Label as security and @ mention @gitlab-com/gl-security/appsec
  • The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
  • Security reports checked/validated by a reviewer from the AppSec team
Edited by Andrew Smith

Merge request reports

Loading