# CircleCI not running as build check on open source project

**URL:** <https://discuss.circleci.com/t/circleci-not-running-as-build-check-on-open-source-project/33947>\
**Category:** Integrations and Accounts\
**Created:** [January 2, 2020, 10:36am UTC](https://discuss.circleci.com/t/circleci-not-running-as-build-check-on-open-source-project/33947 "2020-01-02T10:36:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![aaime](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/aaime/32/23909_2.png) [@aaime](https://discuss.circleci.com/u/aaime)\
**Post date:** [January 2, 2020, 10:36am UTC](https://discuss.circleci.com/t/circleci-not-running-as-build-check-on-open-source-project/33947/1 "2020-01-02T10:36:37Z")

</div>

I’m trying to get CircleCI build the pull request on an open source project I’m developing on.  
I have the configuration setup:

> <https://github.com/geotools/geotools/blob/master/.circleci/config.yml>

The webook is setup too, and PR are one of the events triggering the requests.  
And yet, the build does not show up among the build checks, while Travis and AppVeyor work regularly, here is a random example:

> <https://github.com/geotools/geotools/pull/2732>

The Circle CI checks shows up every now and then only, mostly on my PRs, while I would like it to work for anyone’s PRs instead, and systematically. What am I missing?

---

<div class="post-metadata">

**Author:** ![angelisa](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/angelisa/32/22776_2.png) [@angelisa](https://discuss.circleci.com/u/angelisa)\
**Post date:** [January 3, 2020, 7:02pm UTC](https://discuss.circleci.com/t/circleci-not-running-as-build-check-on-open-source-project/33947/2 "2020-01-03T19:02:12Z")

</div>

Hi @aaime, welcome to the CircleCI Community! Can you or an organization admin for `geotools` confirm a few troubleshooting steps:

1. Are you following a fork of `geotools/geotools` on your own CircleCI account, i.e. `yourGHusername/geotools`? If so please unfollow the project on your account and trigger a new commit.
2. You did mention webhooks are present, but can you confirm the payload is sending a 200 message? This could be an issue with a stale webhook or GitHub’s rate limiting ([https://developer.github.com/v3/#rate-limiting](https://developer.github.com/v3/#rate-limiting)).
3. In your repo’s advanced settings ([https://circleci.com/gh/geotools/geotools/edit#advanced-settings](https://circleci.com/gh/geotools/geotools/edit#advanced-settings)), confirm whether the setting `Build forked pull requests` is On or Off.
4. Also in your repo’s advanced settings, confirm whether `GitHub Status updates` is On or Off.
5. From your org-level settings ([https://circleci.com/gh/organizations/geotools/settings#vcs](https://circleci.com/gh/organizations/geotools/settings#vcs)) confirm GitHub Checks is set up and the repo `geotools/geotools` is listed.
6. Was there a recent change in the organization’s name, repo name or your username?

If you are still having issues, you can submit a ticket to Support with more specific information including your GitHub username, webhook details and other information that might be relevant so we can get to the bottom of this.