Can I prevent pipelines from triggering on certain branches?

Hi, I’ve been trying to configure CircleCI so that it only triggers testing when commits are made to master. I got that all working using workflow filtering, but now the dashboard shows this any time a commit is made to a branch that isn’t master:

Is there any way to prevent the pipeline from triggering entirely so that those messages don’t show up?

Hi @t-urey, welcome to our community!

As far as I know there’s no way to do what you ask right now. What you can do is filter the pipelines to only show those on a particular branch.

Can you please explain your use case? I am particularly interested in understanding why you do not want to create pipelines on non-default branches.


Hey @stig – I have a use case for this same particular feature request. My pipeline’s workflow currently deploys to multiple environments after approvals… once to a staging environment and then once to a prod environment. I’m now setting up the workflow to move a branch pointer whenever those deploys are successful, so that I can always see easily in git which commit hash is deployed to which environment. Now, when pipeline x deploys to the staging environment and moves the ‘staging’ branch pointer, it kicks off pipeline x+1. When pipeline x deploys to the prod environment and moves the ‘prod’ branch pointer, it kicks off pipeline x+2. I can easily make these extra pipelines no-ops with job filters, but I would prefer to have them never created at all for readability/clarity.