# Issue: PR build using wrong commit entirely (Migrated from GitHub)

**URL:** <https://travis-ci.community/t/issue-pr-build-using-wrong-commit-entirely-migrated-from-github/1153>\
**Category:** Travis CI Discussions & Feedback\
**Tags:** issues-migrated\
**Created:** [November 30, 2018, 7:58pm UTC](https://travis-ci.community/t/issue-pr-build-using-wrong-commit-entirely-migrated-from-github/1153 "2018-11-30T19:58:37Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![native-api](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/native-api/32/430_2.png) [@native-api](https://travis-ci.community/u/native-api)\
**Post date:** [December 2, 2018, 3:08am UTC](https://travis-ci.community/t/issue-pr-build-using-wrong-commit-entirely-migrated-from-github/1153/2 "2018-12-02T03:08:01Z")

</div>

Travis gets the source [from a special Github’s ref linked to the PR](https://travis-ci.community/t/travis-ci-branch-expected-waiting-for-status-to-be-reported/829/12?u=native-api), there’s no way to detect if Github “pulled the rug from underneath us” and changed its contents midway.

So the expected behavior would probably be to cancel the build if the PR branch is force-pushed (not sure if regular pushing also applies).

---

_[View the full topic](https://travis-ci.community/t/issue-pr-build-using-wrong-commit-entirely-migrated-from-github/1153)._