CircleCI doesn't notice when Github default branch is updated


#1

Hi,

I recently enabled the “build only pull requests” setting for a repo and also changed the default branch from master to dev. I expected pushes to dev to trigger new builds, but that doesn’t seem to be the case–when I look at dev builds they all say “not run” with a message about the “build only pull requests” setting, until I manually re-trigger the build. On repositories where the default branch has been dev from the start, pushes to dev trigger builds as normal even when the “build only pull requests” setting is selected.

I’d really appreciate any suggestions for a how to resolve this for the specific repo–some tooling that I just wrote depends on building when pull requests are initiated, but it’s very annoying to not get our default branch built!

Thanks,
Ben


#2

@benkuhn Same problem. Is there any updates on this issue?


#3

We are also experiencing the exact same issue. +1 can someone from circleci look into it?


#4

I’m having the same issue. Has anyone found a solution?

Edit with some more details:
We were formerly running successfully with CircleCI with our default branch as develop. All commits to our develop branch were being automatically built and triggering deploys. We switched our default branch to master. Commits are no longer being automatically built. However, commits to develop are still being automatically built. How do we specify to CircleCI that it needs to build from a different default branch?


#5

Here is some follow up from CircleCI support, these steps worked for us to fix the issue:

This will usually resolve itself, given a little time, but you can speed this up by resetting the webhooks. To do this:

  1. Remove all CircleCI webhooks and services from your GitHub or Bitbucket repo settings. (Check under Settings > Webhooks on the relevant service.)
  2. Tell the project to stop building on CircleCI through “Project settings”. (Click the gear icon in the upper right corner of the page listing all recent builds for that project.)
  3. Add the project back on CircleCI.

#6