I have my circle.yml setup so that it builds only master branch. general: branches: only: - master It correctly triggers build on commits to master and ignores commits on other branches. However any pull request from another branch into master does not trigger a build. How can I structure my circle.yml to build all commits into master as well as all pull requests from other branches into master. I’m sure this is a common enough scenario and may be possible with some tweaks to yml file? Any help appreciated. Thanks!

Hi, our product team triages new features from the Feature Requests category here on Discuss. If the workarounds in this thread don’t deliver what you need, then I’d look through the feature request topic to see if someone has already requested this, and “heart” the post to show your support. If you can find one, then you can create one. I found a few similar ones here: PRs should also build the temporary merge with target branch Trigger new build on PR

There are really a lot of cases when user needs to trigger additional new build once PR was opened. In our CI case environment is changing when user opened PR against different target branches. Eg. environment differs depending on v1.3 in this case: armab wants to merge 1 commit into v1.3 from feature/branching You can’t know that ^^ v1.3 for PRs with 1 commit, because CircleCI reuses status from previous build, once you open PR. Without this feature we have this case: User opened PR and got OK green status PR is merged and errored, because env is different ^^ BTW Travis has this option.

I also would love to see this feature. Building on a push is great, but I also want to build on the merge commit that GitHub creates for every pull request (i.e. the head of the pr/ /merge branch that GitHub creates). I understand it results in more load on CircleCI’s servers, but it seems important to test the actual result of merging a pull request, and not just the commit itself (which might be tens or hundreds of commits behind the target branch). There’s a real risk that even without merge conflicts, the tests may pass for the commit but fail once it is merged. Additionally, I need this functionality in order to support a downstream build system I’ve pieced together using CircleCI’s experimental build parameters on their API. Without it, the process will only work if another push is made to the PR after it is opened. It looks like this functionality has also been requested in several other threads: https://discuss.circleci.com/t/show-test-results-for-prospective-merge-of-a-github-pr/1662 [image] How can i setup github pull requests to generate a build? Build Environment i want to add specific behavior for pull requests for that i need the pull request itself to generate a new build, and it doesn’t seem to do that (on travis for example it does, configurable by me). The point is that i might have a release branch ready for release and deploy code that changes and commits the app version(increase revision, naming the version name like the branch name) merges the release branch pull request (if exists) to master, delete the release branch, tag the master with th… Also related: https://discuss.circleci.com/t/feature-request-option-to-disable-builds-on-commit-pushes/682

Any updates on this? Triggering builds on PR mades within a repo (not only coming from forked ones) is a very useful feature, specially when it comes to private repositories.

I’ll chime in also asking if there are any updates or plans to support this.

Bump. Anything Circle team? I switched over from travis because Circle is much more friendly with iOS work, but without this feature I may need to switch back.

From CircleCI.com/changelog/ there’s this: Only PR builds We have added functionality to only run builds when a pull request is open. To enable this functionality you can navigate to “Advanced Settings” for your project and enable the “Only build pull requests” option. This will still build your default branch, which typically is master. Does this sound like a proper solution to this issue in this thread?

Hey Feliciano, Thanks for the update. Having some issues with the workflow. I have enabled the Build on PRs feature, and enabled status check on PRs in github. What happens is PR never triggers builds, and report status always stays greyed out on github. Any suggestions? thanks.

@FelicianoTech: No, this doesnt solve the issue. Please have a look at your competitor Travis to get an idea of how to do it right. This is a basic functionality of a paid CI engine and is a deal breaker for most of us.

Is there a way for circle to trigger a build on the branch specified by pull_request[“head”][“ref”] via https://developer.github.com/v3/activity/events/types/#pullrequestevent? If Circle can do that, and pass this along to my test script (maybe through ENV) I think this would be a good workaround since I can write the logic myself in the script to exit 0 immediately if its not a pullrequestevent.

Pull requests not triggering build

Build Environment

dimfried August 27, 2017, 7:30pm 24

oh thanks man. this did help me a lot

Topic		Replies	Views
Is it possible to run workflows when Github PRs are opened? Build Environment github , workflow , pull-requests	3	21292	November 17, 2020
Circle not triggering on pull requests Build Environment	3	1584	June 29, 2017
Build only pull request to a specific branch Build Environment	12	25018	November 8, 2016
Builds not being triggered from github pull requests Bug Reports	2	1388	January 18, 2018
Trigger CI also when PR created Build Environment github	4	780	January 23, 2024

Pull requests not triggering build

Related topics