In my last post I talked about setting up a basic deployment pipeline using marker branches in git to keep track of what was where. In this post I want to go into a little more detail describing how these marker branches work. To do that I’ll walk through a simple example showing the state of a git repo as code moves through being committed, being pushed to master, deployed to pre-prod, and finally promoted to prod.
