Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
03461544
Commit
03461544
authored
Aug 02, 2021
by
Kyle Wiebers
Committed by
Lin Jen-Shin
Aug 02, 2021
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Improve the documentation for Danger from forks
parent
58776173
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
9 additions
and
5 deletions
+9
-5
doc/development/dangerbot.md
doc/development/dangerbot.md
+9
-5
No files found.
doc/development/dangerbot.md
View file @
03461544
...
...
@@ -151,12 +151,16 @@ at GitLab so far:
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
is not shared to forks. To work around this, you can add an
[
environment
variable
](
../ci/variables/index.md
)
called
`DANGER_GITLAB_API_TOKEN`
with a
is not shared to forks.
### 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
)
to your fork that has the
`api`
scope set. That way the danger comments are made
from CI using that API token instead. Making the variable
[
masked
](
../ci/variables/index.md#mask-a-cicd-variable
)
makes sure it
to your fork that has the
`api`
scope set.
1.
Making the variable
[
masked
](
../ci/variables/index.md#mask-a-cicd-variable
)
makes sure it
doesn't show up in the job logs. The variable cannot be
[
protected
](
../ci/variables/index.md#protect-a-cicd-variable
)
, as it needs
to be present for all feature branches.
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment