# Avoiding triggering builds when pushing from CircleCI **URL:** \ **Category:** Build Environment\ **Tags:** nodejs, circle-yml\ **Created:** [November 1, 2017, 3:22pm UTC](https://discuss.circleci.com/t/avoiding-triggering-builds-when-pushing-from-circleci/17795 "2017-11-01T15:22:44Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![tanepiper](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/tanepiper/32/14866_2.png) [@tanepiper](https://discuss.circleci.com/u/tanepiper)\ **Post date:** [November 1, 2017, 3:22pm UTC](https://discuss.circleci.com/t/avoiding-triggering-builds-when-pushing-from-circleci/17795/1 "2017-11-01T15:22:44Z")
I have a situation where I do the following in my `beta` branch - I do all my normal pipeline but at the end I have a distribution step that does a npm version and publishes a beta version of my module. It then pushes back to the CIRCLE\_BRANCH on the origin to create the tag and update the package.json file for the project with the correct beta tag. I want to also roll this out to my master branch so that it automatically publishes my modules. However whenever I trigger the build from a push to the branch and it completes, this then triggers another build based on the commit just made from CircleCI - and as you guessed it just goes into an infinite loop of distributions. Is there a way to tell CircleCi not to build a push (I’ve seen something about `[ci skip]` but that doesn’t appear in the 2.0 documentation ---
**Author:** ![FelicianoTech](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/felicianotech/32/21348_2.png) [@FelicianoTech](https://discuss.circleci.com/u/FelicianoTech)\ **Post date:** [November 1, 2017, 5:05pm UTC](https://discuss.circleci.com/t/avoiding-triggering-builds-when-pushing-from-circleci/17795/2 "2017-11-01T17:05:00Z")
Yes, `[skip ci]` (or `[ci skip]`) is your solution. Where would you expect to find that in the 2.0 Docs? ---
**Author:** ![tanepiper](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/tanepiper/32/14866_2.png) [@tanepiper](https://discuss.circleci.com/u/tanepiper)\ **Post date:** [November 2, 2017, 11:46am UTC](https://discuss.circleci.com/t/avoiding-triggering-builds-when-pushing-from-circleci/17795/3 "2017-11-02T11:46:21Z")
Hi, yes I eventually got it working. Maybe somewhere near [https://circleci.com/docs/2.0/workflows/#using-contexts-and-filtering-in-your-workflows](https://circleci.com/docs/2.0/workflows/#using-contexts-and-filtering-in-your-workflows) It’s a shame this available at the filter level to just not create jobs, instead of just not running them ---
**Author:** ![system](https://global.discourse-cdn.com/circleci/original/3X/5/1/511608acda8e85906e15909b57bd0a46c1dbe291.png) [@system](https://discuss.circleci.com/u/system)\ **Post date:** [June 18, 2018, 11:40am UTC](https://discuss.circleci.com/t/avoiding-triggering-builds-when-pushing-from-circleci/17795/4 "2018-06-18T11:40:02Z")