Closed pusewicz closed 11 years ago
It doesn't tag unless you run the deploy
task. That's by design, because you don't want to be tagging something as released when it's not actually the running code. How would you expect this to work in your workflow?
deploy:migrations
is different from deploy:migrate
.
The latter does not deploy, whereas deploy:migrations
does actually deploy AND run the migrations.
Ah I see. I've somehow never noticed that task as it wasn't a workflow I've ever used. deploy:migrate
of course I have used many times. I wonder why the task structure is such that deploy:migrations
does not calldeploy
. In any case, thanks, I'll merge your pull. Thanks for the feedback.
I had to manually run
cap production git:tagdeploy