# Inconsistency between commit and PR builds **URL:** \ **Category:** Drone Support\ **Created:** [February 19, 2018, 3:38pm UTC](https://drone.discourse.group/t/inconsistency-between-commit-and-pr-builds/9475 "2018-02-19T15:38:27Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![bradrydzewski](https://yyz1.discourse-cdn.com/flex003/user_avatar/drone.discourse.group/bradrydzewski/32/3513_2.png) [@bradrydzewski](https://drone.discourse.group/u/bradrydzewski)\ **Post date:** [February 19, 2018, 6:56pm UTC](https://drone.discourse.group/t/inconsistency-between-commit-and-pr-builds/9475/2 "2018-02-19T18:56:38Z")
This is a known issues with CI systems like Drone, Travis, Apveyor, etc which use the merge ref to clone the pull requests. There are plans to change the pull request clone logic in a future release, which is discussed in the following thread: > [@Pipeline Event Merge Requests w/GitLab](http://discuss.harness.io/t/planned-change-to-git-clone-logic/1165): > > Hello – I am having issues getting my pipeline to trigger when a Merge Request is created in GitLab and am unsure if this is possible. I have two scenarios I would like to try out: Execute Drone pipeline once a Merge Request is created OR Once the Drone pipeline succeeds create a Merge Request in Gitlab For option 1) I have tried adding the following in my pipeline but unfortunately doesn’t kickoff the pipeline once I create a merge request in my branch\_name: kind: pipeline type: docker… --- _[View the full topic](https://drone.discourse.group/t/inconsistency-between-commit-and-pr-builds/9475)._