diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-01-08 15:08:01 +0000 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-01-08 15:08:01 +0000 |
| commit | a7df1d8717d39424ced032d9fe063f08f97e19d6 (patch) | |
| tree | f887841557b509e950475176baa4d405bfd411f4 /doc/development | |
| parent | e3e300557f5def9bf2271735c8a620e6820dfada (diff) | |
| download | gitlab-ce-a7df1d8717d39424ced032d9fe063f08f97e19d6.tar.gz | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development')
| -rw-r--r-- | doc/development/dangerbot.md | 14 |
1 files changed, 13 insertions, 1 deletions
diff --git a/doc/development/dangerbot.md b/doc/development/dangerbot.md index 40eb4294617..51f7a18dd08 100644 --- a/doc/development/dangerbot.md +++ b/doc/development/dangerbot.md @@ -119,4 +119,16 @@ at GitLab so far: ## Limitations - [`danger local` does not work on GitLab](https://github.com/danger/danger/issues/458) -- Danger output is not added to a merge request comment if working on a fork. +- Danger output is not added to a merge request comment if working 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 + variable](../ci/variables/README.md) called + `DANGER_GITLAB_API_TOKEN` with a personal API token to your + fork. That way the danger comments will be made from CI using that + API token instead. + Making the variable + [masked](../ci/variables/README.md#masked-variables) will make sure + it doesn't show up in the job logs. The variable cannot be + [protected](../ci/variables/README.md#protected-environment-variables), + as it needs to be present for all feature branches. |