Replies: 2 comments 1 reply
-
I don't use GitLab, so I'm afraid you'll probably have to think out a good way to make this work on your own I'm afraid |
Beta Was this translation helpful? Give feedback.
1 reply
-
We use settings/ci_cd/General pipelines to configure the remote yml file to solve this problem. But I am still curious about whether we plan to add this feature in the future. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We have several repositories, one contains
dangerflie.js
and the other contains project files.Gitlab allows multi-project to trigger others Pipeline, we use it to deal with dangerfile related things.
But the current danger does not seem to support this feature. Pipeline is successfully triggered, but the context obtained by dangerjs is not the context of the project we want.
So can you add related features for
danger ci
to support this scenario, such asdanger ci --for-remote-pr https://gitlab.com/ower/repo/~/merge_requests/xx
?Or give us some advices?
https://docs.gitlab.com/ee/ci/pipelines/multi_project_pipelines.html
Beta Was this translation helpful? Give feedback.
All reactions