Context

When CodeRabbit performs a review on GitLab it will create a new Pipeline. This is how GitLab webhook third party integrations typically run. Occasionally this can cause an issue when the following criteria are met:

• CodeRabbit passes its review and approves the MR

• The customer's internal CI pipeline fails

In this situation, GitLab will show that all the pipelines succeeded, despite the fact that the CI actually failed

Answer

There is a known issue on GitLab's side that acknowledges this issue.

There are two workarounds for this:

1) Disable Commit Status from the CodeRabbit configuration which will prevent CodeRabbit from creating a pipeline at all.

2) For third party tools GitLab, suggests triggering them as part of your CI, rather than running the pipelines simultaneously.

This is possible with CodeRabbit using labels. You can create a label that triggers CodeRabbit upon assignment of the label. Then you can have your CI pipeline assign that label when the relevant jobs have completed.