Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
cml pr trigger CI pipelines on GitLab
See original GitHub issueFollowing 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).
Issue Analytics
- State:
- Created a year ago
- Reactions:3
- Comments:16 (16 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
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!