# Restarting a build on PRs

**URL:** <https://drone.discourse.group/t/restarting-a-build-on-prs/9830>\
**Category:** Drone Support\
**Created:** [September 21, 2017, 12:32pm UTC](https://drone.discourse.group/t/restarting-a-build-on-prs/9830 "2017-09-21T12:32:55Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![allanrenucci](https://yyz1.discourse-cdn.com/flex003/user_avatar/drone.discourse.group/allanrenucci/32/3878_2.png) [@allanrenucci](https://drone.discourse.group/u/allanrenucci)\
**Post date:** [September 21, 2017, 12:32pm UTC](https://drone.discourse.group/t/restarting-a-build-on-prs/9830/1 "2017-09-21T12:32:55Z")

</div>

Running Drone 0.8-RC5.

When I start a build on a PR, drone will fetch the HEAD of the PR branch. If I push new commits and restart an old build then drone will pick up these commits.

If this is the expected behaviour, then it is confusing because when you restart a build the web UI will show the hash of the commit that triggered the build in the first place and not the hash of the HEAD of the PR branch.

---

<div class="post-metadata">

**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:** [September 21, 2017, 2:37pm UTC](https://drone.discourse.group/t/restarting-a-build-on-prs/9830/2 "2017-09-21T14:37:36Z")

</div>

Plugins are responsible for cloning. What you are describing is a quirk of the git clone plugin. See [https://github.com/drone-plugins/drone-git/issues/41](https://github.com/drone-plugins/drone-git/issues/41)