# An Adapted Git-Flow Branching Strategy for Development and Releases

DevFeed: [An Adapted Git-Flow Branching Strategy for Development and Releases](<https://devfeed.tech/articles/almost-git-flow-30556.md>)

Original publisher: [Read original article](<https://ryanharter.com/blog/2013/07/almost-git-flow/>)

Published: 2013-07-31T07:00:00Z

Content type: opinion

Language: en

Sources: [Blogs on Ryan Harter](<https://devfeed.tech/sources/blogs-on-ryan-harter.md>)

Topics: [Git](<https://devfeed.tech/topics/git.md>), [Development](<https://devfeed.tech/topics/development.md>), [releases](<https://devfeed.tech/topics/releases.md>)

Tags: [git](<https://devfeed.tech/tags/git.md>), [release](<https://devfeed.tech/tags/release.md>), [workflow](<https://devfeed.tech/tags/workflow.md>)

## AI overview

The article describes the author's adaptation of Git-Flow, using a main development branch, temporary release branches, feature branches, and version tags. It explains why the author uses different branch naming and workflow conventions for developer-focused repositories.

## Source excerpt

I recently shared how I use Git to automatically track my versions. There's quite a bit more to my git workflow than just tagging versions, though, so I'd like to dive into my git usage just a little more. One of my clients introduced me to a very popular, and useful, git branching strategy commonly called Git-Flow based on Vincent Driessen's branching model. I highly recommend reading his article, it's quite good and describes a very useful branching model.