Supply --danger_id when running Danger so Danger accounts don't step on each others

We ask wider community contributors to add DANGER_GITLAB_API_TOKEN so they can run Danger from their forks, however when we trigger a pipeline within gitlab-org/gitlab>, our Danger account cannot update their Danger comment because it's no longer a maintainer.

Here's one of the examples: !82694 (comment 875642328)

Supplying --danger-id to separate the comments should resolve this: https://github.com/danger/danger/blob/75027285ff5970d948ebfd934b51181aedd9ee62/lib/danger/commands/runner.rb#L66

What to fill for --danger-id?

  • Project id from the pipeline project?
  • User id from the Danger account?
  • Hash digest from the token itself?

References

Edited by Lin Jen-Shin