But do you Git the Flow?
A couple of days ago there was a small discussion on Twitter that started with a single question about tagging in git during release cycles. This came from our one and only chairman of the developers oversight committee, Bigbruuutthhhaaa.
The question initially drew all kinds of responses, but we all settled on the fact that we were all pretty much saying the same things albeit differently.
The diagram below shows an illustration how and when to tag and the process flow to typically follow. The initial diagram that this was drafted from was a diagram initially posted by Alex Di Mango, the Head of Engineering at Limehome and it looks something like
Here we have the journey of a single (or multiple) ticket(s), moving gradually from stage to stage during a release cycle. It starts off in the Develop Branch, moves into its own branch and keeps at this until it finally gets merged back to the Master Branch. Because the question was about tags, this post focuses on a common use case highlighted by the diagram (the small tag label there).
Tags are typically created to mark the spot of a concluded release. Whether this release houses a new feature, a bug fix or some chore is up to the team to determine.
