vasdee / git-tag-flow Goto Github PK

Hello,
Huge thanks for this great specification of the GTF. I've something similar except for the deployment process.
In fact, it is a good idea to use tag and this awesomely described pattern, to trigger deployment. The only drawback is that you loose the clear view of the deployment history. You will new tooling to gather those information.

This leads to what I wanted to point out: the rollback workflow. It looks like it you wanted to do a rollback you will need to delete/recreate the tag or use a tag pattern like rollback/<env>/<version>. Have talked out this? What are your thoughts on this?

Looking forward to hear from you
Regards

This is how we all be working in a few years. Git-flow doesn't work. How many teams discussions are centered around complicated branching graphs? I've seen this work well for teams.

Demonstrate using git-tag-flow by generating the PDF artefact via a release tag

Consider adding a footnote on rollback and some guidelines around it could operate with a roll back or roll forward strategy.

Tag flow isn't prescriptive about this, as every solution will be different, with different infrastructure that may/may not be physically able to rollback.

See #9 for some background