Commit f9bfde01 authored by Bob Van Landuyt's avatar Bob Van Landuyt

Document how to use dangerbot from forks

This explains how to workaround one of the dangerbot limitations.
parent 16f76007
...@@ -119,4 +119,16 @@ at GitLab so far: ...@@ -119,4 +119,16 @@ at GitLab so far:
## Limitations ## Limitations
- [`danger local` does not work on GitLab](https://github.com/danger/danger/issues/458) - [`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.
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