# How can I prevent CircleCI from triggering builds on PR to upstream repository?

**URL:** <https://discuss.circleci.com/t/how-can-i-prevent-circleci-from-triggering-builds-on-pr-to-upstream-repository/21975>\
**Category:** Build Environment\
**Created:** [April 25, 2018, 3:41pm UTC](https://discuss.circleci.com/t/how-can-i-prevent-circleci-from-triggering-builds-on-pr-to-upstream-repository/21975 "2018-04-25T15:41:12Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![nma](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/nma/32/18327_2.png) [@nma](https://discuss.circleci.com/u/nma)\
**Post date:** [April 25, 2018, 3:41pm UTC](https://discuss.circleci.com/t/how-can-i-prevent-circleci-from-triggering-builds-on-pr-to-upstream-repository/21975/1 "2018-04-25T15:41:12Z")

</div>

Hi,

I’m working on helping an open source project migrate from Circle 1.0 to Circle 2.0, and I setup my own Circle CI on my forked repo.

[github.com/upstream/repo.git](http://github.com/upstream/repo.git)  
[github.com/mygit/repo.git](http://github.com/mygit/repo.git)

When I test a PR on mygit/repo/branch -\> upsream/repo/master, instead of the upstream’s CircleCI process, it runs my version of CircleCI (which had some missing environment variables and failed)

Is there a way to prefer the upstream configuration, since their CircleCI environment variables are the most up to date.

Thanks!

---

<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, 3:41pm UTC](https://discuss.circleci.com/t/how-can-i-prevent-circleci-from-triggering-builds-on-pr-to-upstream-repository/21975/2 "2018-07-24T15:41:14Z")

</div>

Closed on July 24, 2018, 3:41pm UTC

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