4 ms·
This is what I use tags for. Master = deployable state (stable) Every deploy gets a tag (named with its version). Rollback to previous tag in event of failure
by debaserab2 7y ago
This is what I use tags for.
Master = deployable state (stable)
Every deploy gets a tag (named with its version). Rollback to previous tag in event of failure. Deployments remain just as predictable.
- mikekchar 7y agoI've also seen people have a single development branch and multiple release branches (imagine a 'devel' branch that everyone merges into and a branch for each release that you have, and that potentially merges back into devel if you do hot patches). It's essentially the same thing -- branches aren't really all that different than tags in git.
- debaserab2 7y agoYeah its basically aesthetics. I do like keeping the release identifier separate from branches though just for categorization purposes (branches = development, tags = releases)