# Pull Requests builds use forked repo config file

**URL:** <https://discuss.circleci.com/t/pull-requests-builds-use-forked-repo-config-file/6074>\
**Category:** Bug Reports\
**Tags:** circle-yml\
**Created:** [September 6, 2016, 5:50pm UTC](https://discuss.circleci.com/t/pull-requests-builds-use-forked-repo-config-file/6074 "2016-09-06T17:50:39Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![WesleyBatista](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/wesleybatista/32/13580_2.png) [@WesleyBatista](https://discuss.circleci.com/u/WesleyBatista)\
**Post date:** [September 6, 2016, 5:50pm UTC](https://discuss.circleci.com/t/pull-requests-builds-use-forked-repo-config-file/6074/1 "2016-09-06T17:50:40Z")

</div>

When I open a PR the forked repo triggers a build CircleCI.

The problem is that the build triggered runs on my CircleCI project using the config file on the forked repo, which leads to errors on the builds, once the machine is configured differently and have different environment vars.

I noticed that if I disable my project then the builds triggered by the forked repo runs on their own CircleCI project.

Could somebody please help me on this? Maybe it is a setting that I am missing?

---

<div class="post-metadata">

**Author:** ![teohhanhui](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/teohhanhui/32/12069_2.png) [@teohhanhui](https://discuss.circleci.com/u/teohhanhui)\
**Post date:** [April 25, 2018, 7:36pm UTC](https://discuss.circleci.com/t/pull-requests-builds-use-forked-repo-config-file/6074/2 "2018-04-25T19:36:45Z")

</div>

I still have this issue with CircleCI 2.0 builds.

Before I disabled the CircleCI project for my fork, the build is **only** run in the CircleCI project for the fork.

[https://circleci.com/workflow-run/c4e4b2a1-f75f-4c0e-8399-5f8fbe29e0b6](https://circleci.com/workflow-run/c4e4b2a1-f75f-4c0e-8399-5f8fbe29e0b6)

After I disabled the CircleCI project for my fork, the build is run in the parent repository, as expected.

[https://circleci.com/workflow-run/2d636bcb-4808-43a8-9db1-feff0e1f5633](https://circleci.com/workflow-run/2d636bcb-4808-43a8-9db1-feff0e1f5633)

Whether a CircleCI project exists for a fork **should not** affect the pull request builds on the parent repository.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/circleci/original/3X/5/1/511608acda8e85906e15909b57bd0a46c1dbe291.png) [@system](https://discuss.circleci.com/u/system)\
**Post date:** [July 24, 2018, 7:36pm UTC](https://discuss.circleci.com/t/pull-requests-builds-use-forked-repo-config-file/6074/3 "2018-07-24T19:36:48Z")

</div>

Closed on July 24, 2018, 7:36pm UTC

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
