# Converting a draft PR into a ready-for-review PR creates a second Github Check

**URL:** <https://travis-ci.community/t/converting-a-draft-pr-into-a-ready-for-review-pr-creates-a-second-github-check/8562>\
**Category:** Travis CI Discussions & Feedback\
**Tags:** github-integration, travis-build\
**Created:** [May 11, 2020, 5:04pm UTC](https://travis-ci.community/t/converting-a-draft-pr-into-a-ready-for-review-pr-creates-a-second-github-check/8562 "2020-05-11T17:04:57Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Situphen](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/situphen/32/4139_2.png) [@Situphen](https://travis-ci.community/u/Situphen)\
**Post date:** [May 11, 2020, 5:04pm UTC](https://travis-ci.community/t/converting-a-draft-pr-into-a-ready-for-review-pr-creates-a-second-github-check/8562/1 "2020-05-11T17:04:57Z")

</div>

Steps to reproduce:

1. Create a Draft PR
2. Mark the PR as ready for review (maybe it needs to be done while a build is running, I am not sure)

What is expected: Only one Github Check for Travis CI

What is seen: Two Github Checks for Travis CI, one working fine and another one stuck in the " Build Created" state

Examples :

- [https://github.com/zestedesavoir/zds-site/pull/5742](https://github.com/zestedesavoir/zds-site/pull/5742)
- [https://github.com/zestedesavoir/zds-site/pull/5784](https://github.com/zestedesavoir/zds-site/pull/5784)

---

<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:** [May 11, 2020, 9:49pm UTC](https://travis-ci.community/t/converting-a-draft-pr-into-a-ready-for-review-pr-creates-a-second-github-check/8562/2 "2020-05-11T21:49:26Z")

</div>

Seeing that there’s only one Travis check at both links and the 2nd one is succeeded, this must be an instance of

> [@GitHub status not posted on commits on repositories using legacy Service integration](https://travis-ci.community/t/github-status-not-posted-on-commits-on-repositories-using-legacy-service-integration/7798/9):
>
> We have a few more details to share on this subject. In the last couple of weeks, we have observed an increased number of failures to post statuses on GitHub. The sources of the increase itself remains unclear, but the repeated problems prompted us to clean up some wasteful requests. This helped a little, but not entirely; at the height of the user activities, we still saw some errors. We reached out to GitHub, and was granted some additional (but temporary) capacity so that our services can c…

---

<div class="post-metadata">

**Author:** ![Situphen](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/situphen/32/4139_2.png) [@Situphen](https://travis-ci.community/u/Situphen)\
**Post date:** [May 11, 2020, 11:00pm UTC](https://travis-ci.community/t/converting-a-draft-pr-into-a-ready-for-review-pr-creates-a-second-github-check/8562/3 "2020-05-11T23:00:19Z")

</div>

I don’t think so because we switched from the legacy integration to Github Apps more than one month ago and the issue seems to happen only with draft PR.

I will try to get a better understanding of when the issue happen with my team. Don’t hesitate to ask if you need more information on something!