cml: cml pr trigger CI pipelines on GitLab
Following this message on Discord: https://discord.com/channels/485586884165107732/728693131557732403/978973993338044456
When the command cml pr --merge dvc.lock
is executed as part of a GitLab CI pipeline, a new MR is created (as expected) and CI pipeline for that commit is triggered, which creates a new MR, etc. (loop of CI pipelines)
If you look at the pipelines you will see several consecutive automatically triggered pipelines. Same if you look in the MRs (closed by me).
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 3
- Comments: 16 (16 by maintainers)
Here you go: https://github.com/iterative/cml/pull/1035
PS: I would have preferred to first add tests and then make the changes, but I have never worked with js, and I don’t have the time to figure out how to set up the development environment.
It was my pleasure 😃 thank you for the guidance!
It doesn’t seem very difficult to make these couple of changes, shall I create a MR for you? 😃
If we are adding
[ci skip]
gitlab might be not honouring it (again)?