How to prevent builds in conflicted PRs?

Travis CI Discussions & Feedback
1

Hi all! I’m trying to figure out if there’s a way to keep Travis from running a build on a PR which is currently in a conflicted state. Looking at Building Pull Requests - Travis CI , it says:

So when you create or update a pull request, and Travis CI doesn’t create a build for it, make sure the pull request is mergeable. If it isn’t, rebase it against the upstream branch and resolve any merge conflicts. When you push the fixes up to the pull request, Travis CI will happily build them.

… which I would interpret to mean no build should start on a conflicted PR, yet that’s what’s happening. Is this a bug, possibly a regression? Or do I have to configure something in order to get the desired behaviour out of Travis? Seems like a waste of resources to have it run builds on unresolved merges…

2

Hi @sixtyfive,

I recommend reading this:

This in particular:

So when you create or update a pull request, and Travis CI doesn’t create a build for it, make sure the pull request is mergeable. If it isn’t, rebase it against the upstream branch and resolve any merge conflicts. When you push the fixes up to the pull request, Travis CI will happily build them.

3

Interesting. So the fact that Travis is building my conflicted PRs means I’m hitting a bug.

Is it a known one, @Montana?

4

Hi @sixtyfive,

What is the repo name in particular where you’re running into this issue? You can DM me, or just post it here.