Why Are Pipelines That Do Not Listen to Code Commit Events Still Triggered Upon Code Commits?

Symptom

Pipelines that do not listen to code commit (push) events are still triggered upon code commits.

Root Cause

• You have changed and committed code of the source branch of an unclosed merge request.
• You have selected Merge request and Update events at the same time when setting pipeline triggers.
  Figure 1 Merge request trigger
  

Solution

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.