Help Center/
CodeArts Pipeline/
FAQs/
Functions/
Why Are Pipelines That Do Not Listen to Code Commit Events Still Triggered Upon Code Commits
Updated on 2024-10-12 GMT+08:00
Why Are Pipelines That Do Not Listen to Code Commit Events Still Triggered Upon Code Commits
Reasons:
- You have changed code of the source branch of the merge request (not closed) and committed code.
- You have selected Merge request and Update events at the same time when setting pipeline triggers.
Figure 1 Merge request trigger
When you modify the source branch code of an unclosed merge request and commit code, an update event is generated. If the target branch of the merge request is within the listening range, the corresponding pipeline will be triggered.
Parent topic: Functions
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot