NOTE - this workaround is no longer supported
fake_deploy_for_cci2 a required name? I followed the workaround convention but modified
fake_deploy_for_cci2 to my liking and changed the
commands values, and my tagged builds are still not triggering in CircleCI 2.0.
# Deploy to staging for git tags prefixed with 'qa-'
mkdir -p src/assets /web/coverage
My tag has been pushed to GitHub as
(clearly I've caved to the workaround as it's holding us back)
EDIT: I've realized my mistake - reading too quickly. Thanks, all. I think this will work for us for now. We would still love to be updated if anything involving this workaround (or the official implementation) changes!