# Status check created for an internal PR but not for an external one **URL:** \ **Category:** Travis CI Discussions & Feedback\ **Tags:** github-integration, github-build-check\ **Created:** [April 14, 2020, 5:19pm UTC](https://travis-ci.community/t/status-check-created-for-an-internal-pr-but-not-for-an-external-one/8149 "2020-04-14T17:19:49Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![csgeek](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/csgeek/32/3859_2.png) [@csgeek](https://travis-ci.community/u/csgeek)\ **Post date:** [April 14, 2020, 5:19pm UTC](https://travis-ci.community/t/status-check-created-for-an-internal-pr-but-not-for-an-external-one/8149/1 "2020-04-14T17:19:49Z")
I have a repo setup where before a merge can occur into a branch it requires: 1. a Code Review 2. a Successful build of a pull request. If I push a feature branch to my repo and create a PR that works fine, but IF the contributor fork the project and then created a PR the PR never triggers a build. Has anyone ran into this type of issue before? ---
**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:** [April 14, 2020, 11:01pm UTC](https://travis-ci.community/t/status-check-created-for-an-internal-pr-but-not-for-an-external-one/8149/2 "2020-04-14T23:01:21Z")
Could you give example links? I suspect that the 2nd PR rather has some error that prevents a build. ---
**Author:** ![csgeek](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/csgeek/32/3859_2.png) [@csgeek](https://travis-ci.community/u/csgeek)\ **Post date:** [April 15, 2020, 1:08am UTC](https://travis-ci.community/t/status-check-created-for-an-internal-pr-but-not-for-an-external-one/8149/3 "2020-04-15T01:08:10Z")
Sure. > Usually I have the code execute a PR request. My .travis config is [here](https://github.com/GeekBeacon/geekbeacon-docs/blob/master/.travis.yml) This is a different PR that has the usual check offs though it’s based on a feature branch from the same repo. > Any thoughts? ---
**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:** [April 15, 2020, 1:36am UTC](https://travis-ci.community/t/status-check-created-for-an-internal-pr-but-not-for-an-external-one/8149/4 "2020-04-15T01:36:54Z")
[https://travis-ci.com/github/GeekBeacon/geekbeacon-docs/requests:](https://travis-ci.com/github/GeekBeacon/geekbeacon-docs/requests:) ![2020-04-15 04_36_15-GeekBeacon_geekbeacon-docs - Travis CI](https://us1.discourse-cdn.com/flex015/uploads/travis_ci/original/2X/4/4dc3e46c896e2830bd3756430d626f5acffd57b4.png) ---
**Author:** ![csgeek](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/csgeek/32/3859_2.png) [@csgeek](https://travis-ci.community/u/csgeek)\ **Post date:** [April 15, 2020, 2:15am UTC](https://travis-ci.community/t/status-check-created-for-an-internal-pr-but-not-for-an-external-one/8149/5 "2020-04-15T02:15:38Z")
Interesting, what does “Abuse Detected” mean? ---
**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:** [April 15, 2020, 2:19am UTC](https://travis-ci.community/t/status-check-created-for-an-internal-pr-but-not-for-an-external-one/8149/6 "2020-04-15T02:19:42Z")
Exactly what it says on the tin (c). They use various heuristic checks that they obviously don’t divulge. You can however guess possible reasons [from past topics](https://travis-ci.community/search?q=%22abuse%20detected%22). E.g. this one looks relevant: > [@Some PR are not analyzed with message "Abuse detected"](https://travis-ci.community/t/some-pr-are-not-analyzed-with-message-abuse-detected/1191): > > On our project [https://travis-ci.org/Dolibarr/dolibarr/](https://travis-ci.org/Dolibarr/dolibarr/) , all PR of one of our contributor are not analyzed. They appeared with message Abuse detected in the page [https://travis-ci.org/Dolibarr/dolibarr/requests](https://travis-ci.org/Dolibarr/dolibarr/requests) Why ? How can i fix this ?