# GitHub Build Settings

**URL:** <https://forum.buildkite.community/t/github-build-settings/3066>\
**Category:** General\
**Created:** [July 19, 2023, 6:51pm UTC](https://forum.buildkite.community/t/github-build-settings/3066 "2023-07-19T18:51:09Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![OwenCR](https://avatars.discourse-cdn.com/v4/letter/o/e5b9ba/32.png) [@OwenCR](https://forum.buildkite.community/u/OwenCR)\
**Post date:** [July 19, 2023, 6:51pm UTC](https://forum.buildkite.community/t/github-build-settings/3066/1 "2023-07-19T18:51:09Z")

</div>

Is it possible to have the following build configuration in github without expressing it in the Filter Build Conditional language:

- Build all commits on `master`
- Build all commits on `production`
- Build all pull requests

I’m trying to migrate my repo from building all branches to the above configuration. But I don’t want to interrupt my deploys on `master` and `production`.

---

<div class="post-metadata">

**Author:** ![stephanie.atte](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.buildkite.community/stephanie.atte/32/1357_2.png) [@stephanie.atte](https://forum.buildkite.community/u/stephanie.atte)\
**Post date:** [July 19, 2023, 8:47pm UTC](https://forum.buildkite.community/t/github-build-settings/3066/2 "2023-07-19T20:47:04Z")

</div>

Hey @OwenCR

Thanks for reaching out!

Apart from using [Conditional expressions](https://buildkite.com/docs/pipelines/conditionals) you can use Branch Filter Pattern and GitHub Settings on your pipeline. Make sure you don’t have “Skip pull request builds for existing commits” when you select Build Pull Request

Go to pipeline setting → select Github

Cheers!

---

<div class="post-metadata">

**Author:** ![OwenCR](https://avatars.discourse-cdn.com/v4/letter/o/e5b9ba/32.png) [@OwenCR](https://forum.buildkite.community/u/OwenCR)\
**Post date:** [July 19, 2023, 10:01pm UTC](https://forum.buildkite.community/t/github-build-settings/3066/3 "2023-07-19T22:01:48Z")

</div>

Ah! I wasn’t sure if `Branch Limiting` would exclude my Pull Request branches.

To be sure, are you suggesting similar settings in the UI to the attached screenshots?

 ![image](https://us1.discourse-cdn.com/flex016/uploads/buildkite1/original/2X/f/fcd9f9801e62e5ab76a4a768034f965127bf77a3.png)  
 ![image](https://us1.discourse-cdn.com/flex016/uploads/buildkite1/original/2X/a/a37be4f183f522d08f3ce287af88f706a5d43e7f.png)

---

<div class="post-metadata">

**Author:** ![OwenCR](https://avatars.discourse-cdn.com/v4/letter/o/e5b9ba/32.png) [@OwenCR](https://forum.buildkite.community/u/OwenCR)\
**Post date:** [July 19, 2023, 10:28pm UTC](https://forum.buildkite.community/t/github-build-settings/3066/4 "2023-07-19T22:28:14Z")

</div>

> Make sure you don’t have “Skip pull request builds for existing commits” when you select Build Pull Request

With this setting off, if I push 50 commits up, then open a PR, only the tip would get built in Buildkite.  
Whereas with the setting on, if I do the same thing, 50 builds get triggered in Buildkite.

Is that correct?

---

<div class="post-metadata">

**Author:** ![stephanie.atte](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.buildkite.community/stephanie.atte/32/1357_2.png) [@stephanie.atte](https://forum.buildkite.community/u/stephanie.atte)\
**Post date:** [July 19, 2023, 11:08pm UTC](https://forum.buildkite.community/t/github-build-settings/3066/5 "2023-07-19T23:08:44Z")

</div>

@OwenCR If I understand your question correctly. This setting will only work if turned on prior to all these though

So if you have “Skip pull request builds for existing commits” and a for that commit that already started then any other builds on the same commit will be skipped