Our gh-pages branch is just documentation which means no tests get run but circle kicks off a build when changes are pushed to this branch. We recently updated documentation deployment so that every master build would refresh the docs and therefore push to gh-pages. These gh-pages builds are noisy (they send a "No tests: mapzen/lost on gh-pages" email) and unnecessary. This PR updates circle to not run builds for changes to the gh-pages branch
Overview
Our
gh-pagesbranch is just documentation which means no tests get run but circle kicks off a build when changes are pushed to this branch. We recently updated documentation deployment so that everymasterbuild would refresh the docs and therefore push togh-pages. Thesegh-pagesbuilds are noisy (they send a "No tests: mapzen/lost on gh-pages" email) and unnecessary. This PR updates circle to not run builds for changes to thegh-pagesbranchProposed Changes
https://circleci.com/docs/2.0/configuration-reference/#branches