From e83862ae7c8bdd42e8182b6042d9b37f62e2bdc9 Mon Sep 17 00:00:00 2001 From: Oli Evans Date: Fri, 6 Mar 2020 09:37:30 +0000 Subject: [PATCH] docs: better explanation of circleci opt-in to tags madness Thanks to @Mr0grog Co-Authored-By: Rob Brackett --- .circleci/config.yml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/.circleci/config.yml b/.circleci/config.yml index 7b41ba2a8..c258a56f0 100644 --- a/.circleci/config.yml +++ b/.circleci/config.yml @@ -369,7 +369,9 @@ workflows: - go-ipfs-http-client - ipfs-webui - # NOTE: You have to opt in to get circleci to trigger builds for a tat. As it is required that you set the tag filter to all dependent jobs, this is pulled out into a seperate workflow. + # NOTE: CircleCI only builds tags if you explicitly filter for them. That + # also means tag-based jobs can only depend on other tag-based jobs, so we + # use a separate workflow because every job needs to be tagged together. # see: https://circleci.com/docs/2.0/workflows/#executing-workflows-for-a-git-tag docker-on-tag: jobs: