Commit 94289eb0 authored by GitLab Bot's avatar GitLab Bot

Automatic merge of gitlab-org/gitlab master

parents 2a9aa29b 14758c6f
...@@ -151,12 +151,16 @@ at GitLab so far: ...@@ -151,12 +151,16 @@ at GitLab so far:
Danger is run but its output is not added to a merge request comment if working Danger is run but its output is not added to a merge request comment if working
on a fork. This happens because the secret variable from the canonical project on a fork. This happens because the secret variable from the canonical project
is not shared to forks. To work around this, you can add an [environment is not shared to forks.
variable](../ci/variables/index.md) called `DANGER_GITLAB_API_TOKEN` with a
### Configuring Danger for forks
Contributors can configure Danger for their forks with the following steps:
1. Add an [environment variable](../ci/variables/index.md) called `DANGER_GITLAB_API_TOKEN` with a
[personal API token](https://gitlab.com/-/profile/personal_access_tokens?name=GitLab+Dangerbot&scopes=api) [personal API token](https://gitlab.com/-/profile/personal_access_tokens?name=GitLab+Dangerbot&scopes=api)
to your fork that has the `api` scope set. That way the danger comments are made to your fork that has the `api` scope set.
from CI using that API token instead. Making the variable 1. Making the variable [masked](../ci/variables/index.md#mask-a-cicd-variable) makes sure it
[masked](../ci/variables/index.md#mask-a-cicd-variable) makes sure it
doesn't show up in the job logs. The variable cannot be doesn't show up in the job logs. The variable cannot be
[protected](../ci/variables/index.md#protect-a-cicd-variable), as it needs [protected](../ci/variables/index.md#protect-a-cicd-variable), as it needs
to be present for all feature branches. to be present for all feature branches.
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment