News for hackers. Stuff that matters.
Re:Please stop recommending Gitflow by debaserab2 on Thursday March 05, 2020 @01:16AM (#22491361)
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.

Re:Please stop recommending Gitflow by mikekchar on Thursday March 05, 2020 @02:11AM (#22491568)
I'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.
Re:Please stop recommending Gitflow by debaserab2 on Thursday March 05, 2020 @03:20PM (#22497713)
Yeah its basically aesthetics. I do like keeping the release identifier separate from branches though just for categorization purposes (branches = development, tags = releases)