The documentation is very generic, with few examples, and a step behind the functionality actually available.
Getting a build to trigger or do certain actions on specific branches or tags seems to be very difficult, and harder to test.
When a commit or tag on a branch is pushed to GIT, it quickly appears in CircleCI - in my case marked as ‘not run’. But it is unclear as to why. There is no further information, the build details page is simply empty.
For example, why does pushing a tagged commit ‘v1.0.0’ get labeled as not run when the circle.yml file starts with the following:
general: branches: only: - staging - /v[0-9]+(\.[0-9]+)*/ deployment: release: tag: /v[0-9]+(\.[0-9]+)*/ commands: - do something
According to the docs, because the tag matches a deployment command, it should run.